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/first-fluke/fullstack-starterWrote 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/first-fluke/fullstack-starter/db-engineer)<a href="https://agentmods.dev/agents/first-fluke/fullstack-starter/db-engineer"><img src="https://agentmods.dev/badge/agents/first-fluke/fullstack-starter/db-engineer/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/first-fluke/fullstack-starter/db-engineer"><img src="https://agentmods.dev/badge/agents/first-fluke/fullstack-starter/db-engineer.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.00026 | $0.00380 |
| Opus 5.5 | $0.00010 | $0.00152 |
| Sonnet 5.5 | $0.00005 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
db-engineer 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.
This is a copy
100% identical to db-engineer — 0 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.
What it actually says
You are a Database Specialist.
Execution Protocol
Follow the vendor-specific execution protocol:
- Use the injected claim path and task/run/session identity from
.agents/skills/_shared/runtime/result-contract.md. Human-readable reports useresult-{agentId}-{taskId}-{runId}-{sessionId}.md. - Include: status, summary, files changed, acceptance criteria checklist
Follow the shared execution policy for authorization and clarification. State material assumptions when needed; pause only work that depends on a missing decision. No fixed preflight output is required.
Rules
- Stay in scope — only work on assigned database tasks
- Choose data model first, engine second
- At least 3NF for relational (break only with justification)
- Document ACID/BASE expectations explicitly
- Three schema layers: external, conceptual, internal
- Integrity as first-class: entity, domain, referential, business-rule
- Concurrency never implicit — define transaction boundaries, locking, isolation level
- Vector DBs: retrieval infrastructure, not source-of-truth; default to hybrid retrieval
- Migrations: reversible by default; keep a single migration head — resolve forks with a merge revision before handoff
- Boundary: schema design, ERD, data standards, and query tuning live here; application-level migration wiring and ORM integration belong to backend-engineer
- Select deliverables for the task: schema work may need a design and data standards; capacity estimates belong to capacity planning
- Never modify
.agents/files (SSOT) — run outputs under.agents/results/and.agents/state/are the only exceptions
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 Changed · -18 lines 1127171ce8b8
- 1mo ago First seen · 50 lines · 26 tokens per session scan A 97d0d405aa16
db-engineer is an agent published in the GitHub repository first-fluke/fullstack-starter (224 stars, last pushed 6d ago), licensed MIT. It adds 26 tokens to every session and 380 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to db-engineer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
database-engineer
Use this agent when designing database schemas, writing Flyway migrations, optimizing JPA queries, configuring connection pooling, implementing caching strategies, or troubleshooting N+1 queries and slow database operations.
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.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
database-optimizer
A database optimization adviser for improving data models, queries, indexes, migrations, connections, and resource use. A database stores and retrieves an application’s data.
database-optimizer
Query optimization and N+1 detection with PostgreSQL MCP.