database-admin

A database administration assistant for working with systems that store and organize application data, such as PostgreSQL, MySQL, and MongoDB.

In plain words
What is it for?
Use it to analyze queries, review schemas and indexes, plan backups and replication, manage permissions, monitor performance, and support data migrations.
Why use it?
It helps investigate slow queries, unreliable databases, access issues, and risks around backups or data loss.

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/vidcap-mcp-server/database-admin
Clone the repo
git clone --depth 1 https://github.com/mrgoonie/vidcap-mcp-server

Made for: Claude Code.

Per session 63 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 912 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.00063 $0.00912
Opus 5 $0.00032 $0.00456
Sonnet 5 $0.00013 $0.00182
Haiku 4.5 $0.00006 $0.00091

Measured 2d ago against content hash 88a0a6feede3, 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: NNN-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 · 63 tokens per session scan A 88a0a6feede3

Subscribe to this mod's changes

database-admin is an agent published in the GitHub repository mrgoonie/vidcap-mcp-server (9 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 912 once invoked, about $0.0003 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-31.

Related

Other agents, from other repositories

ecto-schema-designer

Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.

oliver-kriska/claude-elixir-phoenix · 30 tokens

database-engineer

PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.

yonatangross/orchestkit · 28 tokens

Quality Advisor

Background SQL reviewer. Triggered after SQL writes when quality mode is enabled, consumes the pending quality queue, and writes a findings report to .cocoplus/.

Snowflake-Labs/cocoplus · 35 tokens

database-architect

Database design, optimization, and operations expert. Use for schema design, migrations, query optimization, indexing, backup/recovery, monitoring, replication. Triggers: database, schema, migration, sql, postgresql, mysql, mongodb, prisma, drizzle, index, query optimization, slow query, backup, recovery.

softspark/ai-toolkit · 67 tokens

db2-dba

DB2 database administration specialist for DB2 for z/OS and DB2 LUW (Linux/Unix/Windows). Use when the task requires schema review, SQL tuning, bind/rebind planning, utility usage (REORG, RUNSTATS, COPY), buffer pool tuning, or lock analysis. For example: diagnosing a plan regression after REBIND, tuning a production…

josstei/maestro-orchestrate · 303 tokens

data-architect

Data Architect subagent for the design-architecture skill. Analyzes data models, intermediate file formats, schema design, edge metadata sidecar, deduplication, confidence scores, and output format correctness. Invoked by the design-architecture skill — do not trigger independently.

SenolIsci/mykg · 59 tokens