database-admin

A database administration agent for working with systems that store application data, including relational databases such as PostgreSQL and MySQL and NoSQL systems such as MongoDB.

In plain words
What is it for?
Use it to design tables and indexes, analyse query performance, plan backups and replication, troubleshoot databases, manage permissions, and handle data migrations.
Why use it?
It helps investigate slow queries, unreliable databases, unsafe permissions, backup problems, and other data-system issues.

Agent for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/mrgoonie/human-mcp/database-admin
Clone the repo
git clone --depth 1 https://github.com/mrgoonie/human-mcp

Made for: Claude Code.

Per session 395 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,255 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00395 $0.01255
Opus 5 $0.00198 $0.00628
Sonnet 5 $0.00079 $0.00251
Haiku 4.5 $0.00040 $0.00126

Measured 2d ago against content hash 4c5d5403d30e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

.claude/agents/database-admin.md · 87 lines

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:

  1. 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 psql or appropriate database CLI tools to gather diagnostic information
    • Review existing table structures, indexes, and relationships
    • Analyze query patterns and performance metrics
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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 psql for 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/reports directory to each other with this file name format: YYMMDD-from-agent-name-to-agent-name-task-name-report.md.

Read the full file on GitHub · 87 lines

Changes

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.

  1. 2d ago First seen · 87 lines · 0 tokens per session scan A 4c5d5403d30e

Subscribe to this mod's changes

database-admin is an agent published in the GitHub repository mrgoonie/human-mcp (295 stars, last pushed 5mo ago), licensed MIT. It adds 395 tokens to every session and 1,255 once invoked, about $0.0020 per session on Opus 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.

Related

Other agents, from other repositories

hierarchical

Files called AGENTS.md commonly appear in many places inside a container - at "/", in "", deep within git repositories, or in any other directory; their location is not limited to version-controlled folders.

limecloud/lime · 0 tokens

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.

glittercowboy/taches-cc-resources · 45 tokens

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.

glittercowboy/taches-cc-resources · 46 tokens

grader

You are an assertion grading agent. Your job is to evaluate whether assertions about a skill's output are satisfied, verify factual claims, and critique the quality of the evaluation itself.

laborany/laborany · 0 tokens

frontend-specialist

Senior Frontend Architect who builds maintainable React/Next.js systems with performance-first mindset. Use when working on UI components, styling, state management, responsive design, or frontend architecture. Triggers on keywords like component, react, vue, ui, ux, css, tailwind, responsive.

danstrem2/clawdbot-skill-master-pack · 63 tokens

mobile-developer

Expert in React Native and Flutter mobile development. Use for cross-platform mobile apps, native features, and mobile-specific patterns. Triggers on mobile, react native, flutter, ios, android, app store, expo.

danstrem2/clawdbot-skill-master-pack · 47 tokens