Add: Supabase database administrator agent for managing and securing … #541
Conversation
There was a problem hiding this comment.
Pull request overview
This pull request adds a new Supabase database administrator agent to help users build, manage, and secure Supabase databases using the Supabase MCP server.
- Introduces a comprehensive agent for Supabase database administration with PostgreSQL and RLS expertise
- Includes a flexible mode-aware system supporting both Supabase database operations and JSONL file-based storage
- Provides extensive security auditing capabilities and best practices guidance
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| agents/supabase-dba.agent.md | New agent file with comprehensive instructions for Supabase database development, migration management, security implementation, and dual-mode operation (Supabase/JSONL) |
| docs/README.agents.md | Adds entry for the new Supabase database administrator agent in the alphabetically-sorted agents table |
| --- | ||
| description: "Expert Supabase database developer and administrator using the Supabase MCP server for building, managing, and securing Supabase databases." | ||
| name: "supabase database administrator" | ||
| tools: ["codebase", "edit/editFiles", "githubRepo", "extensions", "runCommands", "mcp_supabase_list_organizations", "mcp_supabase_get_cost", "mcp_supabase_confirm_cost", "mcp_supabase_create_project", "mcp_supabase_list_projects", "mcp_supabase_get_project", "mcp_supabase_list_tables", "mcp_supabase_list_extensions", "mcp_supabase_list_migrations", "mcp_supabase_apply_migration", "mcp_supabase_execute_sql", "mcp_supabase_get_logs", "mcp_supabase_get_project_url", "mcp_supabase_get_anon_key", "mcp_supabase_generate_typescript_types", "mcp_supabase_create_branch", "mcp_supabase_list_branches", "mcp_supabase_delete_branch", "mcp_supabase_reset_branch"] | ||
| --- |
There was a problem hiding this comment.
The agent file should include a model field in the front matter to specify which model the agent is optimized for. This is strongly encouraged in the coding guidelines for agent files. For example, you could add model: GPT-4.1 or another appropriate model identifier based on which model this agent has been optimized for.
There was a problem hiding this comment.
@copilot open a new pull request to add model: "gpt-4" (#541 (comment))
1 participant
…databases
Pull Request Checklist
npm startand verified thatREADME.mdis up to date.Description
Type of Contribution
Additional Notes
By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.