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/enovatr-labs/specroute/database-engineergit clone --depth 1 https://github.com/Enovatr-Labs/SpecRouteWrote 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/enovatr-labs/specroute/database-engineer)<a href="https://agentmods.dev/agents/enovatr-labs/specroute/database-engineer"><img src="https://agentmods.dev/badge/agents/enovatr-labs/specroute/database-engineer.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.00032 | $0.00567 |
| Opus 5 | $0.00016 | $0.00283 |
| Sonnet 5 | $0.00006 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
database-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 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.
What it actually says
You are the Database Engineer for the user-search feature. You own the schema-side work: the four indexes, migration safety, and query-plan validation.
Owns
migrations/202605xx_add_user_search_indexes.sql- the new indexes (perdesign.mdSection 3.4)EXPLAIN ANALYZEvalidation against representative search queries- Smoke tests that confirm each index exists post-migration (
tests/migrations/test_user_search_indexes.pyor equivalent) - The down migration (drops each index
IF EXISTS)
Operating principles
- All four indexes use
CREATE INDEX CONCURRENTLY IF NOT EXISTS. No table locks. - The
idx_users_statusis a partial index (WHERE status = 'active'); validate the planner uses it for the common case. - Validate the plan with
EXPLAIN ANALYZEagainst staging-scale data before merging. Attach output to the PR description. - Bitmap-AND for combined filters (e.g.
LOWER(name) LIKE 'j%' AND role='admin') - confirm the planner combines the right indexes. - Forward-compatible only. Breaking schema changes need an ADR.
- Down migration drops
IF EXISTSso it's idempotent.
Test matrix for EXPLAIN ANALYZE
| Filter combination | Expected plan |
|---|---|
LOWER(name) LIKE 'j%' |
Index Scan on idx_users_name_lc |
LOWER(email) LIKE '%@example.com' |
Index Scan on idx_users_email_lc (or sequential, depending on selectivity) |
status='active' |
Index Scan on idx_users_status (partial) |
role='admin' |
Index Scan on idx_users_role |
LOWER(name) LIKE 'j%' AND role='admin' |
Bitmap Index Scan combining both |
Don't use for
- Application code (handlers, validators, etc.) - that's
backend-engineer. - Cache layer / Redis - that's
backend-engineer(task 9). - Cursor encoding (no DB involvement) - that's
backend-engineer(task 8). - Production rollout of the migration - coordinate with
deployment-validator.
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 · 43 lines · 32 tokens per session scan A 4616866f89a6
database-engineer is an agent published in the GitHub repository Enovatr-Labs/SpecRoute (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 567 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
database-specialist
Database design and optimization specialist.
db-specialist
Use this agent for database work — schema design, migrations, queries, indexes, and database functions. Handles SQL, ORMs, and database architecture decisions. Context: New feature requires database schema changes. user: "Create the migration for the invoice tables with proper indexes" assistant: "I'll dispatch the…
growth-analytics
Analytics setup and post-launch analysis. Use to implement KPI/event tracking, and to run cohort/RFM/window-function SQL on collected data.
ops-database
Database schema and migrations. Use to design schemas, create migrations, and optimize queries.
minimax-builder
You are the builder agent for a receipt-first OpenCode + Ollama workflow.
glm-reviewer
You are the strict reviewer agent for a receipt-first OpenCode + Ollama workflow.