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.
git clone --depth 1 https://github.com/ihatesea69/kiro-kitWrote 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/ihatesea69/kiro-kit/database-admin)<a href="https://agentmods.dev/agents/ihatesea69/kiro-kit/database-admin"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/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/ihatesea69/kiro-kit/database-admin"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/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.00029 | $0.00301 |
| Opus 5.5 | $0.00012 | $0.00120 |
| Sonnet 5.5 | $0.00006 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
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 1mo 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.
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
- Identify the database system, version, and current state
- Gather diagnostics (slow queries, lock contention, resource usage)
- Analyze execution plans and table statistics
- Develop optimization recommendations with expected impact
- Provide executable SQL statements with rollback procedures
- 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
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.
- 1mo ago First seen · 42 lines · 29 tokens per session scan A 0df347d1a600
database-admin is an agent published in the GitHub repository ihatesea69/kiro-kit (19 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 301 once invoked, about $0.0001 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
postgresql-specialist
PostgreSQL database administration, SQL optimization, and schema management specialist with deep PostgreSQL expertise and seamless integration with the Claude Code agent ecosystem.
migration-architect
Plans safe database migrations using the expand-backfill-contract pattern. Never destructive in production.
database-architect
Master Database Architect & Data Engineer. Expert in schema design, query optimization, high-stakes migrations, and modern data platforms (SQL/NoSQL/Vector). Triggers on database, sql, schema, migration, postgres, index, table, normalization.
database-engineer
Thin Claude adapter for database-engineer; canonical brief is authoritative.
cache-strategist
Designs caching strategies. Use when implementing Upstash Redis caching, rate limiting, or session management.
database-optimizer
Optimizes database queries and schema. Use when improving Drizzle ORM queries, Neon Postgres performance, or database structure.