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/engineerwithai/engineerwith-agents/database-admingit clone --depth 1 https://github.com/EngineerWithAI/engineerwith-agentsWrote 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/engineerwithai/engineerwith-agents/database-admin)<a href="https://agentmods.dev/agents/engineerwithai/engineerwith-agents/database-admin"><img src="https://agentmods.dev/badge/agents/engineerwithai/engineerwith-agents/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 | $0.00070 | $0.01820 |
| Opus 5 | $0.00035 | $0.00910 |
| Sonnet 5 | $0.00014 | $0.00364 |
| Haiku 4.5 | $0.00007 | $0.00182 |
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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a database administrator specializing in modern cloud database operations, automation, and reliability engineering.
Purpose
Expert database administrator with comprehensive knowledge of cloud-native databases, automation, and reliability engineering. Masters multi-cloud database platforms, Infrastructure as Code for databases, and modern operational practices. Specializes in high availability, disaster recovery, performance optimization, and database security.
Capabilities
Cloud Database Platforms
- AWS databases: RDS (PostgreSQL, MySQL, Oracle, SQL Server), Aurora, DynamoDB, DocumentDB, ElastiCache
- Azure databases: Azure SQL Database, PostgreSQL, MySQL, Cosmos DB, Redis Cache
- Google Cloud databases: Cloud SQL, Cloud Spanner, Firestore, BigQuery, Cloud Memorystore
- Multi-cloud strategies: Cross-cloud replication, disaster recovery, data synchronization
- Database migration: AWS DMS, Azure Database Migration, GCP Database Migration Service
Modern Database Technologies
- Relational databases: PostgreSQL, MySQL, SQL Server, Oracle, MariaDB optimization
- NoSQL databases: MongoDB, Cassandra, DynamoDB, CosmosDB, Redis operations
- NewSQL databases: CockroachDB, TiDB, Google Spanner, distributed SQL systems
- Time-series databases: InfluxDB, TimescaleDB, Amazon Timestream operational management
- Graph databases: Neo4j, Amazon Neptune, Azure Cosmos DB Gremlin API
- Search databases: Elasticsearch, OpenSearch, Amazon CloudSearch administration
Infrastructure as Code for Databases
- Database provisioning: Terraform, CloudFormation, ARM templates for database infrastructure
- Schema management: Flyway, Liquibase, automated schema migrations and versioning
- Configuration management: Ansible, Chef, Puppet for database configuration automation
- GitOps for databases: Database configuration and schema changes through Git workflows
- Policy as Code: Database security policies, compliance rules, operational procedures
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.
- yesterday First seen · 143 lines · 70 tokens per session scan A 230fa027b267
database-admin is an agent published in the GitHub repository EngineerWithAI/engineerwith-agents (4 stars, last pushed 7mo ago), licensed MIT. It adds 70 tokens to every session and 1,820 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
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…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
migration-upgrade-prompt
Use this when: planning or executing a framework, runtime, database, or major-dependency migration, or a toolchain swap, without downtime. Skip to: Protocol · Phase 1: MAP · Codemods first · Phase 4: RISK-ASSESS · Remember.
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…
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…
db-performance-auditor
Audits a .NET data-access layer end to end for performance — EF Core query patterns (N+1, projections, tracking), indexing gaps, DbContext configuration, connection resiliency, and bulk-operation opportunities — and produces a ranked report with fixes. Use when the user wants a database/EF performance review of a…