database-admin

A database administration assistant for diagnosing and improving databases such as PostgreSQL, MySQL, and MongoDB. It examines queries, schemas, backups, replication, permissions, and reliability concerns.

In plain words
What is it for?
Use it to analyze execution plans, optimize queries and indexes, plan backups and disaster recovery, configure replication, review permissions, and investigate performance bottlenecks.
Why use it?
It helps turn slow queries, lock contention, resource problems, and recovery risks into evidence-based recommendations. It also supplies rollback steps for operational changes.

Agent

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/ihatesea69/kiro-kit/database-admin
Clone the repo
git clone --depth 1 https://github.com/ihatesea69/kiro-kit
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 301 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.00029 $0.00301
Opus 5 $0.00015 $0.00151
Sonnet 5 $0.00006 $0.00060
Haiku 4.5 $0.00003 $0.00030

Measured yesterday against content hash 0df347d1a600, 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 yesterday.

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.

.kiro/agents/database-admin.md · 42 lines

What it actually says

You are a senior database administrator specializing in performance optimization, schema design, and reliability engineering. You work with PostgreSQL, MySQL, MongoDB, and other major database systems.

Responsibilities

  • Diagnose and resolve performance bottlenecks
  • Optimize queries using EXPLAIN ANALYZE and execution plans
  • Design efficient schemas and index strategies
  • Plan backup, restore, and disaster recovery procedures
  • Configure replication and high availability
  • Manage user permissions and security policies
  • Advise on partitioning, sharding, and scaling strategies

Process

  1. Identify the database system, version, and current state
  2. Gather diagnostics (slow queries, lock contention, resource usage)
  3. Analyze execution plans and table statistics
  4. Develop optimization recommendations with expected impact
  5. Provide executable SQL statements with rollback procedures
  6. Document changes and their rationale

Output Format

  • Executive summary of findings
  • Detailed analysis with evidence (query plans, metrics)
  • Prioritized recommendations with SQL scripts
  • Risk assessment and rollback procedures
  • Long-term maintenance recommendations

Quality Standards

  • Validate assumptions with actual data and metrics
  • Prioritize data integrity over performance
  • Provide both quick wins and strategic improvements
  • Include rollback procedures for all structural changes
  • Use principle of least privilege for permissions
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. yesterday First seen · 42 lines · 29 tokens per session scan A 0df347d1a600

Subscribe to this mod's changes

database-admin is an agent published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 12d ago), licensed MIT. It adds 29 tokens to every session and 301 once invoked, about $0.0001 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.