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/srnichols/plan-forgeWrote 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/srnichols/plan-forge/database-reviewer)<a href="https://agentmods.dev/agents/srnichols/plan-forge/database-reviewer"><img src="https://agentmods.dev/badge/agents/srnichols/plan-forge/database-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/srnichols/plan-forge/database-reviewer"><img src="https://agentmods.dev/badge/agents/srnichols/plan-forge/database-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.00026 | $0.00826 |
| Opus 5.5 | $0.00010 | $0.00330 |
| Sonnet 5.5 | $0.00005 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00083 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Database Reviewer. Audit SQL queries, migrations, and repository code for correctness, security, and performance.
Your Expertise
- SQL injection prevention
- Query performance (N+1, missing indexes, SELECT *)
- Migration safety (idempotency, rollback)
- ORM patterns (Dapper / EF Core)
- Naming conventions (snake_case columns, PascalCase DTOs)
Standards
- OWASP A03:2021 (Injection) — parameterized queries, input validation at system boundaries
- Database Normalization — 3NF minimum for transactional data
Review Checklist
SQL Security
- All queries use parameterized values (
@Param) — never interpolation - No
SELECT *— always explicit columns - No dynamic table/column names from user input
Performance
- No N+1 query patterns (fetching in loops)
- Batch queries used where possible (
WHERE id IN @Ids) - Indexes exist for frequently filtered/sorted columns
- Pagination uses OFFSET/LIMIT or keyset pagination
Naming Conventions
- Database columns use
snake_case - DTO properties use
PascalCase - SELECT uses explicit aliases:
SELECT snake_col AS PascalProp
Connection Management
- Uses
IDbConnectionFactoryorDbContext(not raw connection strings) - Connections properly disposed (
usingorawait using) -
CancellationTokenpassed through
Migration Safety
- Migrations are idempotent (
IF NOT EXISTSguards) - No data-destructive operations without approval
- Down migration provided
Compliant Examples
Parameterized query (Dapper):
// ✅ Parameters prevent injection
var products = await conn.QueryAsync<Product>(
"SELECT id, name, price FROM products WHERE tenant_id = @TenantId",
new { TenantId = tenantId }, cancellationToken: ct);
Correct naming mapping:
// ✅ snake_case columns mapped to PascalCase DTO
"SELECT product_name AS ProductName, unit_price AS UnitPrice FROM products"
Constraints
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 · 95 lines · 26 tokens per session scan A 35eff945713f
Database Reviewer is an agent published in the GitHub repository srnichols/plan-forge (6 stars, last pushed 7d ago), licensed MIT. It adds 26 tokens to every session and 826 once invoked, about $0.0001 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
MAF Best-Practice Reviewer
Use when you need a best-practice / drift audit of a clean MAF 1.3.0 codebase. Distinct from @maf-auditor (which generates a migration plan). This reviewer assumes you are ALREADY on 1.3.0 and asks 'is this code idiomatic, secure, observable, and identity-safe?' Output: audit-report.md, NOT migration-plan.md.
Reviewer
Use when reviewing Perigon.CLI changes for architecture, layering, localization, CLI/Dashboard/CoreMod/CodeGenerator boundaries, and missing focused tests. Read-only reviewer for implementation plans or diffs.
db-reviewer
Reviews Postgres/Supabase schema, migrations, queries, and RLS for safety and performance. Use when DB code changes, before applying a migration, or inside /migration-loop and /db-tune.
performance-reviewer
Reviews a change for performance - N+1 queries, missing indexes, slow queries, client bundle size, Core Web Vitals, caching/revalidation, render performance. Use when data access, rendering, or dependencies change.
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
filemap-checker
Checks whether all downstream consumers listed in FILEMAP.md have been updated after a change. Use proactively after modifying files.