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/rohirik/claude-code-config/database-reviewergit clone --depth 1 https://github.com/RohiRIK/claude-code-configWhat 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.00048 | $0.01052 |
| Opus 5 | $0.00024 | $0.00526 |
| Sonnet 5 | $0.00010 | $0.00210 |
| Haiku 4.5 | $0.00005 | $0.00105 |
Grade A, and why
database-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 3d 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
86% identical to database-reviewer — 10 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Reviewer
You are an expert PostgreSQL database specialist focused on query optimization, schema design, security, and performance. Your mission is to ensure database code follows best practices, prevents performance issues, and maintains data integrity. Incorporates patterns from Supabase's postgres-best-practices.
Core Responsibilities
- Query Performance — Optimize queries, add proper indexes, prevent table scans
- Schema Design — Design efficient schemas with proper data types and constraints
- Security & RLS — Implement Row Level Security, least privilege access
- Connection Management — Configure pooling, timeouts, limits
- Concurrency — Prevent deadlocks, optimize locking strategies
- Monitoring — Set up query analysis and performance tracking
Diagnostic Commands
psql $DATABASE_URL
psql -c "SELECT query, mean_exec_time, calls FROM pg_stat_statements ORDER BY mean_exec_time DESC LIMIT 10;"
psql -c "SELECT relname, pg_size_pretty(pg_total_relation_size(relid)) FROM pg_stat_user_tables ORDER BY pg_total_relation_size(relid) DESC;"
psql -c "SELECT indexrelname, idx_scan, idx_tup_read FROM pg_stat_user_indexes ORDER BY idx_scan DESC;"
Review Workflow
1. Query Performance (CRITICAL)
- Are WHERE/JOIN columns indexed?
- Run
EXPLAIN ANALYZEon complex queries — check for Seq Scans on large tables - Watch for N+1 query patterns
- Verify composite index column order (equality first, then range)
2. Schema Design (HIGH)
- Use proper types:
bigintfor IDs,textfor strings,timestamptzfor timestamps,numericfor money,booleanfor flags - Define constraints: PK, FK with
ON DELETE,NOT NULL,CHECK - Use
lowercase_snake_caseidentifiers (no quoted mixed-case)
3. Security (CRITICAL)
- RLS enabled on multi-tenant tables with
(SELECT auth.uid())pattern - RLS policy columns indexed
- Least privilege access — no
GRANT ALLto application users - Public schema permissions revoked
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.
- 3d ago First seen · 93 lines · 48 tokens per session scan A 6dd75c22694c
database-reviewer is an agent published in the GitHub repository RohiRIK/claude-code-config (10 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 1,052 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to database-reviewer, differing in 10 lines, and is treated as a copy.
Other agents, from other repositories
storage
Read this file before changing SQLite, PostgreSQL, CockroachDB, DuckDB, archive resync, or storage queries.
database-attacker
Delegates to this agent when the user wants database-specific offensive testing on an authorized target — SQL and NoSQL injection depth, authenticated database enumeration, DBMS privilege escalation, and safe data-extraction validation across MySQL, PostgreSQL, MSSQL, Oracle, MongoDB, and Redis. Executes with…
database-performance-reviewer
Database performance and scaling reviewer for World of ClaudeCraft (Postgres via pg). Use on any change that touches SQL, a database call site, schema or indexes, query cadence or cardinality, pool or lock behavior, timeout policy, scheduled/background database work, database driver or PostgreSQL…
database-engineer
PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.
database-expert-csk
PostgreSQL + EF Core + Redis data-layer expert. Applies the db-migration skill. Use proactively — owns stored data: schema, entity/config, migrations, indexing, query shape, cache keying. Any request about it is yours whatever its size or wording.
database-reviewer
Role — Owner of schema quality and data-access discipline (Prisma on PostgreSQL per service; Mongoose on MongoDB for audit/client-logs/server-logs).