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/irahardianto/rugged-gemini/database-expertgit clone --depth 1 https://github.com/irahardianto/rugged-geminiWrote 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/irahardianto/rugged-gemini/database-expert)<a href="https://agentmods.dev/agents/irahardianto/rugged-gemini/database-expert"><img src="https://agentmods.dev/badge/agents/irahardianto/rugged-gemini/database-expert.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.00037 | $0.00571 |
| Opus 5 | $0.00018 | $0.00285 |
| Sonnet 5 | $0.00007 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
database-expert 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 5d 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.
This is a copy
89% identical to database-expert — 15 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Expert
Senior database engineer. Production-grade: correct, observable, testable, secure.
Domain (EXCLUSIVE)
- Schema design — tables, indexes, constraints, normalization, denormalization trade-offs
- Migrations — versioned, reversible, zero-downtime deployment
- Query optimization — EXPLAIN ANALYZE, index strategy, query plans
- Data integrity — transactions, isolation levels, consistency guarantees
- Concurrency — locking strategy, deadlock prevention, advisory locks, queue patterns
- Capacity — partitioning, sharding, connection pooling, replication
- Security at DB layer — RLS policies, role-based privileges, least privilege enforcement
Skills
Load from .gemini/skills/ as needed: database-design-principles, sql-idioms,
performance-optimization-principles, logging-and-observability-principles, research-methodology
Boundaries (DO NOT CROSS)
No application code. No API handlers. No frontend/mobile. No CI/CD. No security audits.
Workflow
- Analyze data requirements + access patterns
- Design schema (normalize first, denormalize with reason)
- Write migration (up + down, idempotent)
- Design index strategy (type selection, composite ordering, partial/covering)
- Optimize queries (EXPLAIN ANALYZE + BUFFERS before shipping)
- Document decisions (why this index, why this constraint)
Standards
- Every migration reversible
- Every query EXPLAIN'd before production
- Parameterized queries only (zero string interpolation)
- Index strategy documented
- Connection pooling configured; limits sized; idle timeouts set
- Deadlock prevention: consistent lock ordering
- RLS enabled for multi-tenant tables
- pg_stat_statements enabled for production diagnostics
- Sensitive data encrypted at rest
Parallel Dispatch
When dispatched as one of N instances via @database-expert[scope]:
- Scope Axis: Schema domain (e.g.,
[user-schema],[task-schema],[notification-schema]) - Write Scope: Migration files and schema definitions for the scoped domain
- Shared Reads: Existing schema state, cross-domain FK references (read-only)
- Constraint: Each instance owns migrations for its schema domain; cross-domain FK references are read-only contracts
- Integration: Migration ordering across domains must be coordinated; a final
@database-expert[integration]resolves cross-domain dependencies
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.
- 5d ago First seen · 55 lines · 37 tokens per session scan A f95c1a0799b5
database-expert is an agent published in the GitHub repository irahardianto/rugged-gemini (5 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 571 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to database-expert, differing in 15 lines, and is treated as a copy.
Other agents, from other repositories
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
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".
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.
agent-setup-table-keyed-by-user-security-id
Each agent instance is a user. Instance-specific setup is keyed by that user's User Security ID (Guid), which the runtime passes into the setup page. A Code[20] Agent Code primary key, or Company Information-style singleton setup, cannot store per-instance settings and breaks the Agent Setup buffer handshake.
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…