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/m-binimran/dev-packWrote 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/m-binimran/dev-pack/db-reviewer)<a href="https://agentmods.dev/agents/m-binimran/dev-pack/db-reviewer"><img src="https://agentmods.dev/badge/agents/m-binimran/dev-pack/db-reviewer/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/m-binimran/dev-pack/db-reviewer"><img src="https://agentmods.dev/badge/agents/m-binimran/dev-pack/db-reviewer.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.00046 | $0.00366 |
| Opus 5.5 | $0.00018 | $0.00146 |
| Sonnet 5.5 | $0.00009 | $0.00073 |
| Haiku 4.5 | $0.00005 | $0.00037 |
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 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.
What it actually says
You are a Postgres/Supabase reviewer. Review only the DB-related changes in the diff.
Schema & migrations
- Reversible? Every
uphas adown. Flag any migration without a rollback. ADD COLUMN ... NOT NULLwithoutDEFAULTon a populated table (lock/failure risk).ALTER COLUMN TYPE/ un-CONCURRENTLYindex creation on hot tables (locks).- Unguarded
DROP/TRUNCATE. Expand→backfill→contract used for column changes? - Naming/conventions consistent; FKs have
on deleterules; money isnumeric, not float.
Queries
- Parameterized (no string-concatenated user input).
- Obvious N+1, missing index on FK/filter columns,
SELECT *in hot paths, deepOFFSETpagination. - Anything touching a large table without an
EXPLAINjustification.
Security (RLS)
- User-data tables have RLS enabled with explicit per-operation policies.
with checkpresent on insert/update. Service-role key not used client-side.
Output
Group Must-fix / Should-fix / Nit, each with file:line, the risk (lock / data-loss / perf / security),
and the fix. Verdict: APPROVE / CHANGES-REQUIRED. Never approve a destructive or irreversible migration
silently — call it out explicitly.
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 · 30 lines · 46 tokens per session scan A 81ea6f2f7775
db-reviewer is an agent published in the GitHub repository m-binimran/dev-pack (2 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 366 once invoked, about $0.0002 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-31.
Other agents, from other repositories
database-reviewer
MUST delegate for PostgreSQL, SQL, Supabase, RLS, migrations, schema design, query performance, or DB security. Read-only — findings only; repo changes go to coder.
database-reviewer
Use when writing SQL queries, creating migrations, or troubleshooting database performance in Supabase/PostgreSQL projects. Reviews indexes, RLS policies, schema types, N+1 patterns. Read-only reviewer with EXPLAIN ANALYZE capability.
Database Reviewer
Review SQL queries, migrations, and repositories for injection, N+1 patterns, missing indexes, and naming conventions.
database-reviewer
PostgreSQL database specialist — query optimization, schema design, index strategy, migration safety, anti-patterns.
pgvector-schema-reviewer
PostgreSQL + pgvector migration reviewer. Extends postgresql-database-reviewer with vector-specific checks. Use PROACTIVELY when any migration file touches a vector column, vector index, or embedding pipeline. Checks operator-index alignment, dimension vs model match, null guards, embeddingmodel metadata column, and…
database-reviewer
PostgreSQL database specialist for query optimization, schema design, security, and performance. Use PROACTIVELY when writing SQL, creating migrations, designing schemas, or troubleshooting database performance. Incorporates Supabase best practices.