db-reviewer

A command that reviews PostgreSQL database designs, change scripts, queries, and row-level security rules. Supabase is a service that uses PostgreSQL and adds tools around it.

In plain words
What is it for?
Use it when changing database tables or security rules, writing queries, or checking a migration before applying it.
Why use it?
It helps catch unsafe changes, security problems, and slow queries before they affect a database. Without a target, it reviews the latest code changes.

Command

Install

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.

agentmods
npx agentmods add commands/m-binimran/dev-pack/db-reviewer
Clone the repo
git clone --depth 1 https://github.com/m-binimran/dev-pack
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 99 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00035 $0.00099
Opus 5 $0.00017 $0.00049
Sonnet 5 $0.00007 $0.00020
Haiku 4.5 $0.00003 $0.00010

Measured 2d ago against content hash 2c5d4f1b14fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

commands/db-reviewer.md · 11 lines

What it actually says

/db-reviewer $ARGUMENTS

Launch the db-reviewer subagent to review: $ARGUMENTS

If no target is specified, review the most recent changes (run git diff). Relay the subagent's findings, grouped by severity, with its verdict.

Changes

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.

  1. 2d ago First seen · 11 lines · 35 tokens per session scan A 2c5d4f1b14fa

Subscribe to this mod's changes

db-reviewer is a command published in the GitHub repository m-binimran/dev-pack (2 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 99 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.