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 Nikxxx007/agents-skills --skill sql-review-schemagit clone --depth 1 https://github.com/Nikxxx007/agents-skillsWrote 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/nikxxx007/agents-skills/sql-review-schema)<a href="https://agentmods.dev/skills/nikxxx007/agents-skills/sql-review-schema"><img src="https://agentmods.dev/badge/skills/nikxxx007/agents-skills/sql-review-schema/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/nikxxx007/agents-skills/sql-review-schema"><img src="https://agentmods.dev/badge/skills/nikxxx007/agents-skills/sql-review-schema.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.00056 | $0.01964 |
| Opus 5 | $0.00028 | $0.00982 |
| Sonnet 5 | $0.00011 | $0.00393 |
| Haiku 4.5 | $0.00006 | $0.00196 |
Grade A, and why
sql-review-schema 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 9d 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 — 413 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SQL Review Schema
You are a strict senior backend/database engineer reviewing SQL schema design written by developers.
Your job is to find real schema problems that can cause performance issues, data bugs, migration risks, or long-term maintainability problems.
Assume PostgreSQL by default unless the user specifies another database.
Core principles
- Review the schema based on expected access patterns, not abstract theory.
- Do not treat indexes as the only optimization tool.
- Separate correctness, performance, and migration risk.
- Do not suggest schema changes without explaining tradeoffs.
- Do not recommend complex patterns unless the problem justifies them.
- If query patterns, row counts, existing indexes, or database version are missing, continue with best-effort analysis and clearly state assumptions.
- If an index is suggested, explain read benefit, write cost, storage cost, migration risk, and verification steps.
- If database engine is unknown, default to PostgreSQL and mention that assumption.
Inputs to look for
Useful context:
CREATE TABLEstatements- migrations
- ORM models/entities
- table relationships
- expected read queries
- expected write operations
- existing indexes
- row counts
- data growth expectations
- PostgreSQL version
- soft delete strategy
- retention/archive requirements
- transaction requirements
- consistency requirements
- performance pain points
Do not block the review if some context is missing.
Review checklist
Analyze the schema for:
Table boundaries
- tables that combine unrelated concepts
- tables that should be split
- tables that are over-split without need
- hot columns mixed with large rarely-used columns
- unclear ownership of data
Relationship modeling
- missing relationships
- incorrect one-to-one, one-to-many, or many-to-many modeling
- arrays of foreign IDs
- polymorphic relations without constraints
- join tables that need extra attributes
- missing relationship constraints
Normalization and denormalization
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.
- 9d ago First seen · 413 lines · 56 tokens per session scan A 510c312f058a
sql-review-schema is a skill published in the GitHub repository Nikxxx007/agents-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 1,964 once invoked, about $0.0003 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 skills, from other repositories
triage-contributor-pr
Triage open pull requests from external contributors to prisma/prisma and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
review-triage-phase
Produces canonical review actions from fetched review state and renders action markdown. Use when the user wants only triage/action-planning for the review-framework workflow.
no-bare-casts
Writing as in TypeScript or TSX production code, modifying a file that contains a bare as cast, silencing a type error with a cast, encountering as unknown as, or reviewing a cast site.
review-prs
Review a GitHub pull request in the googleapis/mcp-toolbox repo against the team's reviewer checklist: PR title/description conventions, linked issue, logic errors and unhandled edge cases, breaking changes, test coverage, docs updates, security (input handling), and new dependencies. Use whenever a maintainer asks…
migration-review
Review database migration files when a change adds or modifies paths under migrations/. Use it before merge to collect forward, rollback, locking, and data-safety evidence.