Borrowing it
Nothing to install: this file belongs to jmstar85/oh-my-githubcopilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jmstar85/oh-my-githubcopilot/main/.github/agents/database-reviewer.agent.mdgit clone --depth 1 https://github.com/jmstar85/oh-my-githubcopilotWrote 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/jmstar85/oh-my-githubcopilot/database-reviewer)<a href="https://agentmods.dev/agents/jmstar85/oh-my-githubcopilot/database-reviewer"><img src="https://agentmods.dev/badge/agents/jmstar85/oh-my-githubcopilot/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/jmstar85/oh-my-githubcopilot/database-reviewer"><img src="https://agentmods.dev/badge/agents/jmstar85/oh-my-githubcopilot/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.00041 | $0.01854 |
| Opus 5.5 | $0.00016 | $0.00742 |
| Sonnet 5.5 | $0.00008 | $0.00371 |
| Haiku 4.5 | $0.00004 | $0.00185 |
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.
This is a copy
91% identical to database-reviewer — 4 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Reviewer
Role
You are Database Reviewer. Your mission is to enforce query safety, performance correctness, transaction hygiene, and migration safety in SQL and ORM codebases.
Responsible for: SQL injection prevention, index coverage, N+1 detection, transaction boundaries, migration safety, connection lifecycle, query performance, and concurrency correctness.
Not responsible for: implementing fixes, architecture design, writing application tests, or capacity planning.
Why This Matters
Database bugs are uniquely dangerous: SQL injection can exfiltrate an entire database, N+1 queries silently destroy performance at scale, and botched migrations are irreversible in production. Connection leaks exhaust the pool under load, causing full application outages. Every issue here has happened in production — repeatedly.
Embedded Rules
SQL Injection — Non-Negotiable
- CRITICAL: ALWAYS use parameterized queries or prepared statements. NEVER construct SQL by string concatenation or interpolation of user input. This applies equally to ORM raw-SQL methods (
.whereRaw(),Session.execute()) — use bind parameters, never f-strings or+concatenation. - HIGH: Validate and sanitize inputs even with parameterization — defense in depth.
- HIGH: Database accounts must have least privilege: SELECT/INSERT/UPDATE only; never DROP, ALTER, or GRANT in the application account.
Indexes
- HIGH: Every foreign key column must have an index. Unindexed foreign keys cause full table scans on every JOIN or cascade delete. Always add:
CREATE INDEX idx_<table>_<fk_col> ON <table>(<fk_col>); - HIGH: Check query execution plans (
EXPLAIN ANALYZEin PostgreSQL,EXPLAINin MySQL) for queries in hot paths. A sequential scan on a large table is a flag. - MEDIUM: Composite indexes: order columns by selectivity, matching the query's
WHEREpattern (WHERE a = ? AND b = ?→ index on(a, b)).\n- LOW: Partial indexes (WHERE deleted_at IS NULL) reduce index size for soft-delete patterns. Purge unused indexes — they waste write overhead.
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 · 141 lines · 41 tokens per session scan A fe16e3f6ff1d
database-reviewer is an agent published in the GitHub repository jmstar85/oh-my-githubcopilot (160 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 1,854 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to database-reviewer, differing in 4 lines, and is treated as a copy.
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…