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 skills add Eliyce/paqad-ai --skill database-design-reviewgit clone --depth 1 https://github.com/Eliyce/paqad-aiWrote 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/skills/eliyce/paqad-ai/database-design-review)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/database-design-review"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/database-design-review/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/skills/eliyce/paqad-ai/database-design-review"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/database-design-review.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.00014 | $0.00590 |
| Opus 5 | $0.00007 | $0.00295 |
| Sonnet 5 | $0.00003 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
database-design-review 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 8d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What It Does
Reviews schema and migration changes for correctness, rollout safety, and maintainability, with findings split cleanly across correctness risk, migration safety risk, and performance risk.
Use This When
Use this for any request that changes tables, constraints, nullability, data movement, or migration sequencing, even when the code change seems small.
Inputs
- Read the changed migrations and the closest database docs for the affected module first.
- Read
runtime/capabilities/coding/checklists/database-review-20pt.mdandreferences/database-review-rubric.mdbefore reviewing. - Read any query or index docs that justify the new schema shape.
Procedure
- Run
scripts/scan-migration-smells.sh <migration-files...>to surface candidate hazards (destructive drops, NOT-NULL without default, renames without shim, type changes, table locks, data deletion). - Cross-reference each hit with
assets/safe-migration-rules.txtto decide whether it's actually unsafe in this project's context. - Review schema design (cardinality, defaults, constraints, nullability) and index/FK coverage as judgment work.
- Bucket findings into Correctness / Migration Safety / Performance per
assets/output.template.md. - Validate with
scripts/lint-output.sh.
Output Contract
- Return sections named
Correctness Risks,Migration Safety Risks, andPerformance Risks. - List each finding as one bullet with the exact schema element or migration involved.
- If a bucket has no findings, write
<Bucket Name>: noneexactly.
Escalate / Stop Conditions
- Ask when data volume, deployment sequencing, or rollback expectations are required to judge safety.
- Warn when a migration appears non-additive, irreversible, or likely to lock hot tables.
- Do not wave through undocumented backfills or destructive column changes.
Resources
references/database-review-rubric.mdscripts/scan-migration-smells.shscripts/lint-output.shassets/output.template.mdassets/safe-migration-rules.txtruntime/capabilities/coding/checklists/database-review-20pt.mdagents/openai.yaml
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 69 lines · 14 tokens per session scan A 23086b38e778
database-design-review is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 590 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
database
A database design and migration guide written in Korean. It covers table structure, naming conventions, common columns, indexes, foreign keys, and versioned migration files.
database-verification
Shell-based database connectivity and integrity checks. Verifies that databases are reachable, schemas match expectations, and data integrity constraints hold.
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
x-osv
CLI for Google OSV database. Query vulnerabilities for packages, scan local projects for vulnerable dependencies. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill). Required Tool: Install osv-scanner for project scanning (see https://github.com/google/osv-scanner).
similarity-search-patterns
Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.