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/fmarzochi/egc/database-reviewergit clone --depth 1 https://github.com/Fmarzochi/EGCWrote 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/fmarzochi/egc/database-reviewer)<a href="https://agentmods.dev/agents/fmarzochi/egc/database-reviewer"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/database-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.00041 | $0.00970 |
| Opus 5 | $0.00020 | $0.00485 |
| Sonnet 5 | $0.00008 | $0.00194 |
| Haiku 4.5 | $0.00004 | $0.00097 |
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 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.
This is a copy
91% identical to database-reviewer — 37 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 — 92 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.
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
Key Principles
- Index foreign keys: Always, no exceptions
- Use partial indexes:
WHERE deleted_at IS NULLfor soft deletes - Covering indexes:
INCLUDE (col)to avoid table lookups - SKIP LOCKED for queues: 10x throughput for worker patterns
- Cursor pagination:
WHERE id > $lastinstead ofOFFSET - Batch inserts: Multi-row
INSERTorCOPY, never individual inserts in loops - Short transactions: Never hold locks during external API calls
- Consistent lock ordering:
ORDER BY id FOR UPDATEto prevent deadlocks
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 · 92 lines · 41 tokens per session scan A 67f9a6b6bb3d
database-reviewer is an agent published in the GitHub repository Fmarzochi/EGC (48 stars, last pushed today), licensed Apache-2.0. It adds 41 tokens to every session and 970 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to database-reviewer, differing in 37 lines, and is treated as a copy.
Other agents, from other repositories
test-hunter
Generates adversarial tests for a module or feature. Does NOT write happy-path tests — that is the author's job. Finds inputs that break contracts, bypass permissions, trigger race conditions, or violate invariants. Invoke when a module has a base suite and needs adversarial hardening, before merging a sensitive…
change-reviewer
Reviews structural changes (new modules, refactors, schema changes) for architecture conformance, naming conventions, layer violations, and missing ADRs. Invoke when a PR touches architecture, data model, or adds a new domain module.
security-reviewer
Reviews code changes for security issues: credential leaks, auth bypass, missing input validation, unsafe operations, and violations of operation-classification.md. Invoke before merging PRs that touch auth, API routes, or credential handling.
spec-guardian
Verifies the codebase is in sync with the spec (PRD.md, use-cases.md, ADRs, data-model.md). Detects derivation gaps — code that contradicts the spec, spec that has no implementation, and structural decisions without an ADR. Invoke before cutting a release or when drift is suspected.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
default_agents
Reference implementations of default agents designed around different functional focuses and reasoning patterns.