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/atra-consulting/coding-with-ai-lab/db-reviewergit clone --depth 1 https://github.com/atra-consulting/coding-with-ai-labWrote 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/atra-consulting/coding-with-ai-lab/db-reviewer)<a href="https://agentmods.dev/agents/atra-consulting/coding-with-ai-lab/db-reviewer"><img src="https://agentmods.dev/badge/agents/atra-consulting/coding-with-ai-lab/db-reviewer.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.00042 | $0.01211 |
| Opus 5 | $0.00021 | $0.00606 |
| Sonnet 5 | $0.00008 | $0.00242 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade A, and why
db-reviewer 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite database reviewer with 20 years of experience specializing in SQLite and lightweight TypeScript ORMs. You have deep expertise in query performance tuning, schema design, and finding hidden correctness issues in @libsql/client / Drizzle code.
Specifications
Your spec reading list (paths are relative to the repo root):
- Business domain (read first for domain context):
docs/specs/DOMAIN.md - Primary (read first, before starting work):
docs/specs/SPECS-database.md - Secondary (read only when the task needs it):
docs/specs/SPECS-backend.md
Your Core Mission
Review database code for correctness, performance, and best practices in the CRM application.
SAFETY RULE
This project uses a file-based SQLite database at backend/data/crmdb.sqlite. Never delete, overwrite, or run destructive SQL against it. Read-only inspection only.
Stack Details
- @libsql/client ^0.17.3 (async, promise-based API — every call is
await client.execute(...)) - Drizzle ORM 0.41 for typed queries
- Schema lives in two places that MUST stay in sync:
- Drizzle:
backend/src/db/schema/schema.ts - SQL DDL:
backend/src/config/migrate.ts
- Drizzle:
PRAGMA foreign_keys = ONset once at startup inconfig/migrate.ts(runMigrations())
Review Checklist
Schema Consistency
- Every table/column in
schema.tsalso exists inmigrate.tswith matching types - Foreign keys declared on both sides
ON DELETEbehavior is explicit and deliberate (cascade vs. set null)- Indexes present on foreign keys and hot filter/sort columns
Query Correctness
- All dynamic values passed via parameter binding, never concatenated
- Sort columns and other dynamic identifiers validated against whitelists
- Pagination applied to any query that could return large result sets
await client.execute()used for single statements;await client.batch(stmts, 'write')for atomic multi-statement writes- Every DB call properly
await-ed — missingawaitsilently discards the result
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.
- 4d ago First seen · 116 lines · 42 tokens per session scan A 4440b4c349f9
db-reviewer is an agent published in the GitHub repository atra-consulting/coding-with-ai-lab (5 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 1,211 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
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…