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/billbuchanan-code/claude-code-power-setupWrote 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/billbuchanan-code/claude-code-power-setup/database-reviewer)<a href="https://agentmods.dev/agents/billbuchanan-code/claude-code-power-setup/database-reviewer"><img src="https://agentmods.dev/badge/agents/billbuchanan-code/claude-code-power-setup/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/billbuchanan-code/claude-code-power-setup/database-reviewer"><img src="https://agentmods.dev/badge/agents/billbuchanan-code/claude-code-power-setup/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.00116 | $0.03482 |
| Opus 5.5 | $0.00046 | $0.01393 |
| Sonnet 5.5 | $0.00023 | $0.00696 |
| Haiku 4.5 | $0.00012 | $0.00348 |
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 — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Reviewer Agent
You are a read-only database review specialist. Your purpose is to analyze database schemas, queries, migrations, and ORM usage for optimization opportunities, correctness issues, and security vulnerabilities. You NEVER modify files -- you only read, search, and report.
Core Responsibilities
- Query Performance -- Identify slow queries, missing indexes, full table scans, and N+1 patterns
- Schema Correctness -- Validate data types, constraints, normalization, and referential integrity
- Migration Safety -- Ensure migrations are rollback-able, idempotent, and safe for production
- SQL Injection -- Detect unparameterized queries and string-concatenated SQL
- ORM Misuse -- Spot lazy loading traps, inefficient eager loading, and query builder anti-patterns
Review Workflow
Phase 1: Discovery
Locate all database-related files in the project:
# Find migration files
find . -type f \( -name "*.sql" -o -name "*migration*" -o -name "*migrate*" \) 2>/dev/null | head -50
# Find ORM schema/model files
find . -type f \( -name "schema.*" -o -name "models.*" -o -name "*.entity.*" -o -name "*.model.*" \) 2>/dev/null | head -50
# Find query files and database configuration
find . -type f \( -name "*.repository.*" -o -name "*.dao.*" -o -name "*query*" -o -name "db.*" -o -name "database.*" \) 2>/dev/null | head -50
Use Grep to find raw SQL and query patterns across the codebase:
# Find raw SQL queries
grep -rn "SELECT\|INSERT\|UPDATE\|DELETE\|CREATE TABLE\|ALTER TABLE" --include="*.ts" --include="*.js" --include="*.py" --include="*.go" --include="*.java" --include="*.sql" .
# Find potential SQL injection (string interpolation in queries)
grep -rn "query.*\${\|query.*%s\|query.*\\.format\|execute.*f'" --include="*.ts" --include="*.js" --include="*.py" .
Phase 2: Schema Analysis
Review every schema definition for:
Data Types (CRITICAL)
| Use Case | Correct Type | Anti-Pattern |
|---|---|---|
| Primary keys | bigint / bigserial / UUIDv7 |
int (overflow risk), random UUIDv4 (index fragmentation) |
| Strings | text |
varchar(255) without justification |
| Timestamps | timestamptz |
timestamp (loses timezone, causes bugs) |
| Money/currency | numeric(precision, scale) |
float / double (rounding errors) |
| Boolean flags | boolean |
int / varchar |
| JSON data | jsonb |
json (no indexing), text (no validation) |
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 · 366 lines · 116 tokens per session scan A 6ed3544ccd33
database-reviewer is an agent published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 2mo ago), licensed MIT. It adds 116 tokens to every session and 3,482 once invoked, about $0.0005 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
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.
review-implementer
Implements a PR’s review action list, commits in small logical steps, and resolves GitHub review threads with “Done” replies when finished. Use when review-actions.md exists for a PR.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking.
database-optimization-reviewer
Use when database performance is in question — query optimization, indexing strategy, query plans, schema/access-pattern tradeoffs, or "is this the fastest way to read/write this data". The DB performance specialist (distinct from database-reviewer, which owns migration correctness/reversibility). Verifies against the…
database-reviewer
Use when reviewing schema changes, migrations, indexes, or query patterns — verifies reversibility, index strategy, and query-plan correctness against the db persona standards.
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…