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/ajgreyling/cursor-doctorWrote 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/rules/ajgreyling/cursor-doctor/sql-migrations)<a href="https://agentmods.dev/rules/ajgreyling/cursor-doctor/sql-migrations"><img src="https://agentmods.dev/badge/rules/ajgreyling/cursor-doctor/sql-migrations/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/rules/ajgreyling/cursor-doctor/sql-migrations"><img src="https://agentmods.dev/badge/rules/ajgreyling/cursor-doctor/sql-migrations.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.00000 | $0.00226 |
| Opus 5.5 | $0.00000 | $0.00090 |
| Sonnet 5.5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
sql-migrations 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.
What it actually says
SQL Migration Conventions
cursor-doctor currently has no database schema or migrations. If SQL artifacts are introduced, follow this policy.
File naming
- Use ordered filenames, for example
001-init.sql,002-add-indexes.sql. - Keep one migration concern per file.
Idempotency
- Prefer
IF NOT EXISTS/IF EXISTSguards where supported. - Use upsert patterns (
ON CONFLICT) for seed/reference data. - Avoid destructive statements unless explicitly documented and approved.
Execution discipline
- Apply schema changes before data backfills.
- Wrap dependent operations in explicit transactions where safe.
- Document rollback strategy in migration comments or companion docs.
Documentation updates
- Update
docs/ARCHITECTURE.mdanddocs/DATA_MODEL.mdwhen schema is added or changed.
Completeness checklist
- migration location and naming
- idempotent patterns
- write order if applicable
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 · 37 lines · 0 tokens per session scan A 4c976a1b4a2b
sql-migrations is a cursor rule published in the GitHub repository ajgreyling/cursor-doctor (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 226 tokens. 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 cursor rules, from other repositories
postgresql
PostgreSQL production rules. Safe migrations, parameterized queries, TIMESTAMPTZ, proper indexing strategy.
python-app
Here's how the python application is organized.
supabase-auth-security
Supabase auth security — enforces getUser() over getSession() on the server.
supabase-rls
Supabase Row Level Security enforcement.
query-patterns
Database query patterns, optimization, and safety rules. Apply when writing or editing queries.
schema-design
Database schema design conventions and standards. Apply when designing schema or migrations.