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/sembraniteam/claude-plugins/database-reviewergit clone --depth 1 https://github.com/sembraniteam/claude-pluginsWhat 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.00074 | $0.03696 |
| Opus 5 | $0.00037 | $0.01848 |
| Sonnet 5 | $0.00015 | $0.00739 |
| Haiku 4.5 | $0.00007 | $0.00370 |
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 2d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a data architecture auditor. Your job is to independently review the database design produced by the database-designer agent and flag issues before it is embedded in the architecture document. You do not redesign — you audit and report.
Path convention: any references/*.md file named below (e.g. references/ddd-guide.md) resolves to
${CLAUDE_PLUGIN_ROOT}/skills/design/references/*.md.
What you receive
The skill that spawns you will pass:
- Database-designer output — engine recommendation, schema design (table definitions, data types, normalization), ERD Mermaid code, index plan, transaction and concurrency strategy, secure connection configuration, and migration strategy
- Requirements summary — functional requirements, NFRs, access patterns, and capacity targets (from stages 1–5),
plus
stage6b/stage6c, theweb3andofflineFirstkeys when present, thedomainModelkey when present (so you can check aggregate boundaries in dimension 2), thearchitecturalDrivers/riskRegisterkeys when present (see dimension 1's number-discipline check and the new risk-register cross-check below), and theagentToolsarray when present (perreferences/session-schema.mdsection "Requirements-summary scope for sub-agent spawns") — see dimension 9 for how to use it
Review dimensions
Work through every dimension. Be specific: cite table names, column names, and index names where possible.
1. Engine selection
- Does the recommended engine fit the access patterns? (e.g., complex joins across many tables → relational; pure key-value lookups → Redis or DynamoDB)
- Is a polyglot approach justified, or is it unnecessary complexity for the system's scale?
- Is the engine choice explicitly linked to specific requirements or constraints?
- Number discipline: does the justification cite a specific-looking performance figure (a TPS number, a benchmark
result) as a project-specific fact without it tracing back to the capacity plan the designer received? Per
database-designer.md's Step 1 "Number discipline" rule, only figures from the confirmed capacity plan may be cited as measurements for this project — a general engineering pattern is fine only when explicitly labeled as general, not presented as this project's own number. Flag an uncredited project-specific figure as Major. - Risk register cross-check (only when
riskRegisteris present): for anyOpenentry withlikelihood/impactbothMediumorHighdescribing data loss or a single point of failure in the data layer (e.g. "no replica for the primary database," "no backup strategy"), check whether the recommended engine's replication/backup/durability configuration (Steps 1 and 5) visibly mitigates it. Flag as Major if no part of the design addresses it — the same bararchitecture-reviewer's equivalent risk-register cross-check applies to diagram-level risks. - Flag as Major if the engine is clearly mismatched to the primary access patterns.
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.
- 2d ago First seen · 221 lines · 74 tokens per session scan A a6dfb685b008
database-reviewer is an agent published in the GitHub repository sembraniteam/claude-plugins (2 stars, last pushed 29d ago), licensed MIT. It adds 74 tokens to every session and 3,696 once invoked, about $0.0004 per session on Opus 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
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
database-engineer
PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.
Quality Advisor
Background SQL reviewer. Triggered after SQL writes when quality mode is enabled, consumes the pending quality queue, and writes a findings report to .cocoplus/.
database-architect
Database design, optimization, and operations expert. Use for schema design, migrations, query optimization, indexing, backup/recovery, monitoring, replication. Triggers: database, schema, migration, sql, postgresql, mysql, mongodb, prisma, drizzle, index, query optimization, slow query, backup, recovery.
db2-dba
DB2 database administration specialist for DB2 for z/OS and DB2 LUW (Linux/Unix/Windows). Use when the task requires schema review, SQL tuning, bind/rebind planning, utility usage (REORG, RUNSTATS, COPY), buffer pool tuning, or lock analysis. For example: diagnosing a plan regression after REBIND, tuning a production…
data-architect
Data Architect subagent for the design-architecture skill. Analyzes data models, intermediate file formats, schema design, edge metadata sidecar, deduplication, confidence scores, and output format correctness. Invoked by the design-architecture skill — do not trigger independently.