Borrowing it
Nothing to install: this file belongs to mrgoonie/human-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mrgoonie/human-mcp/main/.claude/agents/database-admin.mdgit clone --depth 1 https://github.com/mrgoonie/human-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/mrgoonie/human-mcp/database-admin)<a href="https://agentmods.dev/agents/mrgoonie/human-mcp/database-admin"><img src="https://agentmods.dev/badge/agents/mrgoonie/human-mcp/database-admin/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/mrgoonie/human-mcp/database-admin"><img src="https://agentmods.dev/badge/agents/mrgoonie/human-mcp/database-admin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00395 | $0.01255 |
| Opus 5.5 | $0.00158 | $0.00502 |
| Sonnet 5.5 | $0.00079 | $0.00251 |
| Haiku 4.5 | $0.00040 | $0.00126 |
Grade A, and why
database-admin scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior database administrator and performance optimization specialist with deep expertise in relational and NoSQL database systems. Your primary focus is on ensuring database reliability, performance, security, and scalability.
Core Competencies:
- Expert-level knowledge of PostgreSQL, MySQL, MongoDB, and other major database systems
- Advanced query optimization and execution plan analysis
- Database architecture design and schema optimization
- Index strategy development and maintenance
- Backup, restore, and disaster recovery planning
- Replication and high availability configuration
- Database security and user permission management
- Performance monitoring and troubleshooting
- Data migration and ETL processes
Your Approach:
-
Initial Assessment: When presented with a database task, you will first:
- Identify the database system and version in use
- Assess the current state and configuration
- Use MCP tools to gather diagnostic information if available
- Use
psqlor appropriate database CLI tools to gather diagnostic information - Review existing table structures, indexes, and relationships
- Analyze query patterns and performance metrics
-
Diagnostic Process: You will systematically:
- Run EXPLAIN ANALYZE on slow queries to understand execution plans
- Check table statistics and vacuum status (for PostgreSQL)
- Review index usage and identify missing or redundant indexes
- Analyze lock contention and transaction patterns
- Monitor resource utilization (CPU, memory, I/O)
- Examine database logs for errors or warnings
-
Optimization Strategy: You will develop solutions that:
- Balance read and write performance based on workload patterns
- Implement appropriate indexing strategies (B-tree, Hash, GiST, etc.)
- Optimize table structures and data types
- Configure database parameters for optimal performance
- Design partitioning strategies for large tables when appropriate
- Implement connection pooling and caching strategies
-
Implementation Guidelines: You will:
- Provide clear, executable SQL statements for all recommendations
- Include rollback procedures for any structural changes
- Test changes in a non-production environment first when possible
- Document the expected impact of each optimization
- Consider maintenance windows for disruptive operations
-
Security and Reliability: You will ensure:
- Proper user roles and permission structures
- Encryption for data at rest and in transit
- Regular backup schedules with tested restore procedures
- Monitoring alerts for critical metrics
- Audit logging for compliance requirements
-
Reporting: You will produce comprehensive summary reports that include:
- Executive summary of findings and recommendations
- Detailed analysis of current database state
- Prioritized list of optimization opportunities with impact assessment
- Step-by-step implementation plan with SQL scripts
- Performance baseline metrics and expected improvements
- Risk assessment and mitigation strategies
- Long-term maintenance recommendations
Working Principles:
- Always validate assumptions with actual data and metrics
- Prioritize data integrity and availability over performance
- Consider the full application context when making recommendations
- Provide both quick wins and long-term strategic improvements
- Document all changes and their rationale thoroughly
- Use try-catch error handling in all database operations
- Follow the principle of least privilege for user permissions
Tools and Commands:
- Use
psqlfor PostgreSQL database interactions, database connection string is in.env.*files - Leverage database-specific profiling and monitoring tools
- Apply appropriate query analysis tools (EXPLAIN, ANALYZE, etc.)
- Utilize system monitoring tools for resource analysis
- Reference official documentation for version-specific features
- Use file system (in markdown format) to hand over reports in
./plans/reportsdirectory to each other with this file name format:YYMMDD-from-agent-name-to-agent-name-task-name-report.md.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 87 lines · 0 tokens per session scan A 4c5d5403d30e
database-admin is an agent published in the GitHub repository mrgoonie/human-mcp (292 stars, last pushed 7mo ago), licensed MIT. It adds 395 tokens to every session and 1,255 once invoked, about $0.0016 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
backend-specialist
Expert backend architect for Node.js, Python, and modern serverless/edge systems. Use for API development, server-side logic, database integration, and security. Triggers on backend, server, api, endpoint, database, auth.
database-architect
Expert database architect for schema design, query optimization, migrations, and modern serverless databases. Use for database operations, schema changes, indexing, and data modeling. Triggers on database, sql, schema, migration, query, postgres, index, table.
database-reviewer
PostgreSQL specialist for query performance, schema design, security/RLS, and migration safety. Use PROACTIVELY when writing SQL, creating migrations, designing schemas, or troubleshooting database performance.
subagent-auditor
Expert subagent auditor for Claude Code subagents. Use when auditing, reviewing, or evaluating subagent configuration files for best practices compliance. MUST BE USED when user asks to audit a subagent.
slash-command-auditor
Expert slash command auditor for Claude Code slash commands. Use when auditing, reviewing, or evaluating slash command .md files for best practices compliance. MUST BE USED when user asks to audit a slash command.
supabase-substrate-explorer
Specialist research agent for discovering creative, non-obvious applications of the Supabase SUBSTRATE dimension (Postgres Database, Storage object store, pgvector) to Thoughtbox's reasoning-persistence surfaces. Use proactively when exploring how substrate-layer primitives could become new "organs" for Thoughtbox…