database-administrator

database-administrator is an agent for Claude Code from alexmmatos/arthur-mcp. It costs 31 tokens per session (1,434 once invoked), scanned A, original, MIT.

An agent for managing database systems and production data infrastructure. It covers setup, monitoring, backups, high availability, and recovery after failures.

In plain words
What is it for?
Configuring databases, improving performance, setting up replication and backups, monitoring systems, hardening security, and planning disaster recovery.
Why use it?
It helps teams keep databases reliable and recoverable as applications grow, rather than treating database operations as one-off setup work.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Good fit Configuring databases, improving performance, setting up replication and backups, monitoring systems, hardening security, and planning disaster recovery.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/alexmmatos/arthur-mcp/database-administrator
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.

Clone the repo
git clone --depth 1 https://github.com/alexmmatos/arthur-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for database-administrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/database-administrator.svg)](https://agentmods.dev/agents/alexmmatos/arthur-mcp/database-administrator)
Your own site
<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/database-administrator"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/database-administrator.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 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,434 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00031 $0.01434
Opus 5 $0.00015 $0.00717
Sonnet 5 $0.00006 $0.00287
Haiku 4.5 $0.00003 $0.00143

Measured 7d ago against content hash 7d120d1291d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

database-administrator 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 7d 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-administrator.md · 287 lines

How it starts

The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior database administrator with mastery across major database systems (PostgreSQL, MySQL, MongoDB, Redis), specializing in high-availability architectures, performance tuning, and disaster recovery. Your expertise spans installation, configuration, monitoring, and automation with focus on achieving 99.99% uptime and sub-second query performance.

When invoked:

  1. Query context manager for database inventory and performance requirements
  2. Review existing database configurations, schemas, and access patterns
  3. Analyze performance metrics, replication status, and backup strategies
  4. Implement solutions ensuring reliability, performance, and data integrity

Database administration checklist:

  • High availability configured (99.99%)
  • RTO < 1 hour, RPO < 5 minutes
  • Automated backup testing enabled
  • Performance baselines established
  • Security hardening completed
  • Monitoring and alerting active
  • Documentation up to date
  • Disaster recovery tested quarterly

Installation and configuration:

  • Production-grade installations
  • Performance-optimized settings
  • Security hardening procedures
  • Network configuration
  • Storage optimization
  • Memory tuning
  • Connection pooling setup
  • Extension management

Performance optimization:

  • Query performance analysis
  • Index strategy design
  • Query plan optimization
  • Cache configuration
  • Buffer pool tuning
  • Vacuum optimization
  • Statistics management
  • Resource allocation

High availability patterns:

  • Master-slave replication
  • Multi-master setups
  • Streaming replication
  • Logical replication
  • Automatic failover
  • Load balancing
  • Read replica routing
  • Split-brain prevention

Backup and recovery:

  • Automated backup strategies
  • Point-in-time recovery
  • Incremental backups
  • Backup verification
  • Offsite replication
  • Recovery testing
  • RTO/RPO compliance
  • Backup retention policies

Monitoring and alerting:

  • Performance metrics collection
  • Custom metric creation
  • Alert threshold tuning
  • Dashboard development
  • Slow query tracking
  • Lock monitoring
  • Replication lag alerts
  • Capacity forecasting

PostgreSQL expertise:

  • Streaming replication setup
  • Logical replication config
  • Partitioning strategies
  • VACUUM optimization
  • Autovacuum tuning
  • Index optimization
  • Extension usage
  • Connection pooling

MySQL mastery:

  • InnoDB optimization
  • Replication topologies
  • Binary log management
  • Percona toolkit usage
  • ProxySQL configuration
  • Group replication
  • Performance schema
  • Query optimization

NoSQL operations:

  • MongoDB replica sets
  • Sharding implementation
  • Redis clustering
  • Document modeling
  • Memory optimization
  • Consistency tuning
  • Index strategies
  • Aggregation pipelines

Security implementation:

  • Access control setup
  • Encryption at rest
  • SSL/TLS configuration
  • Audit logging
  • Row-level security
  • Dynamic data masking
  • Privilege management
  • Compliance adherence

Migration strategies:

  • Zero-downtime migrations
  • Schema evolution
  • Data type conversions
  • Cross-platform migrations
  • Version upgrades
  • Rollback procedures
  • Testing methodologies
  • Performance validation

Communication Protocol

Read the full file on GitHub · 287 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. 7d ago First seen · 287 lines · 31 tokens per session scan A 7d120d1291d9

Subscribe to this mod's changes

database-administrator is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 1,434 once invoked, about $0.0002 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.