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/irahardianto/awesome-agvWrote 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/awesome-agv/database-expert)<a href="https://agentmods.dev/agents/irahardianto/awesome-agv/database-expert"><img src="https://agentmods.dev/badge/agents/irahardianto/awesome-agv/database-expert/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/irahardianto/awesome-agv/database-expert"><img src="https://agentmods.dev/badge/agents/irahardianto/awesome-agv/database-expert.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.00037 | $0.00679 |
| Opus 5.5 | $0.00015 | $0.00272 |
| Sonnet 5.5 | $0.00007 | $0.00136 |
| Haiku 4.5 | $0.00004 | $0.00068 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- database-expert — 89% identical, 15 lines differ
How it starts
The opening of the file, as written. The whole thing — 66 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 .agents/skills/ as needed: guardrails, research-methodology,
structured-spec, postgres-idioms, logging-implementation, agent-protocols
Rules
Auto-loaded from .agents/rules/ when applicable: security-mandate,
rugged-software-constitution, code-idioms-and-conventions,
logging-and-observability-mandate, database-design-principles,
performance-optimization-principles, security-principles
Boundaries (DO NOT CROSS)
No application code. No API handlers. No frontend/mobile. No CI/CD. No security audits.
Phase Participation
- DESIGN phase: Creates schema designs, ERDs, data models, migration strategies. Produces database contracts consumed by builders.
- BUILD phase: Implements schema migrations, writes queries, creates indexes, optimizes data access patterns.
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
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 · 66 lines · 37 tokens per session scan A e61b6484f840
database-expert is an agent published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 9d ago), licensed MIT. It adds 37 tokens to every session and 679 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
code-architect
A software architecture specialist for planning how systems are organized and how their major parts work together.
tdd-implementer
Strict quality-first TDD specialist. Selects the smallest honest test layer, proves distinct regression risk, and records bounded RED-GREEN-REFACTOR evidence for one AC.
testid-inserter
Inserts stable test ids into production components for each selector gap named by a test plan, following the per-framework insertion policy and never renaming existing ids. Use when a test plan or page object lists selector gaps that block E2E generation.
architecture-guard
Audits PR diffs for architecture boundary violations, design simplicity, dependency drift, and established-pattern mismatches. Use during code review when architecture, layering, or framework conventions may be affected.
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
test-writer
Writes tests for existing code in an isolated git worktree, so a large batch of new test files never collides with work in the main checkout. Use when adding coverage to a module or backfilling tests.