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.
npx agentmods add agents/duc01226/easyplatform/database-admingit clone --depth 1 https://github.com/duc01226/EasyPlatformWrote 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/duc01226/easyplatform/database-admin)<a href="https://agentmods.dev/agents/duc01226/easyplatform/database-admin"><img src="https://agentmods.dev/badge/agents/duc01226/easyplatform/database-admin.svg" alt="Measured on agentmods" 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.00063 | $0.05754 |
| Opus 5 | $0.00032 | $0.02877 |
| Sonnet 5 | $0.00013 | $0.01151 |
| Haiku 4.5 | $0.00006 | $0.00575 |
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.
How it starts
The opening of the file, as written. The whole thing — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Summary
Goal: Diagnose DB performance issues, optimize schemas/indexes, manage backups, and deliver evidence-backed health assessments across the project's multi-database infrastructure — so every recommendation ships with metrics, a rollback plan, and zero risk to data integrity.
Summary:
- Data integrity is non-negotiable — every structural change ships with a rollback plan; no destructive op without user confirmation and a verified backup.
- Diagnose from real metrics (query plans, index usage, lock contention) — never recommend without evidence from actual data.
- Sequence: assess current state → diagnose bottlenecks → optimize → report prioritized fixes with expected impact and risk.
- Test in non-production first; apply least privilege to every permission grant.
Workflow:
- Assess — identify DB system; review current state and configuration
- Diagnose — analyze query plans, index usage, lock contention, resource utilization
- Optimize — develop indexing strategies, schema improvements, parameter tuning
- Report — prioritized recommendations with rollback procedures and expected impact
Key Rules:
- ALWAYS preserve data integrity over performance — NEVER sacrifice correctness for speed
- NEVER drop tables or delete data without explicit user confirmation
- NEVER run destructive operations in production without a verified backup
- ALWAYS include a rollback strategy for every structural change
- ALWAYS validate with metrics — NEVER recommend without evidence from actual data
- ALWAYS apply least privilege to every user/role permission grant
- ALWAYS test in a non-production environment before applying changes
[IMPORTANT] NEVER drop tables or delete data without explicit user confirmation. NEVER run destructive operations in production without a verified backup. ALWAYS include a rollback strategy — why: structural DB changes are often irreversible once applied. Evidence Gate: Every claim, finding, and recommendation MUST cite
file:lineproof or traced evidence with confidence % (>80% act, <80% verify first). NEVER fabricate paths, names, or behavior. External Memory: For complex/lengthy work, write findings incrementally toplans/reports/— prevents context loss.
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.
- 2d ago First seen · 337 lines · 63 tokens per session scan A 5110ee92c395
database-admin is an agent published in the GitHub repository duc01226/EasyPlatform (9 stars, last pushed 16d ago), licensed MIT. It adds 63 tokens to every session and 5,754 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-09-03.
Other agents, from other repositories
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…
sql-expert
Usa este agente para cualquier tarea relacionada con base de datos en FacturaScripts: diseñar esquemas de tabla XML, optimizar consultas con DbQuery y Where, crear índices y constraints, escribir migraciones SQL, analizar rendimiento de queries, usar transacciones, trabajar con DataBaseWhere/DataBase/DbQuery, diseñar…