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 rules/ajgreyling/cursor-doctor/sql-migrationsgit clone --depth 1 https://github.com/ajgreyling/cursor-doctorWhat 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.00000 | $0.00226 |
| Opus 5 | $0.00000 | $0.00113 |
| Sonnet 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 yesterday.
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.
- yesterday 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 27d 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
engine-internals
Coding Agent engine implementation details (Cursor + Claude Code) — reference when modifying engine.ts or debugging Agent behavior.
testing-conventions
Testing conventions — must reference when modifying src/ code or tests.
architecture-constraints
GolemBot architecture hard constraints — must check before modifying any src/ code.
app_rules
This document outlines the essential rules and guidelines for developing with the MobileLauncher LT boilerplate. Follow these rules to maintain consistency, scalability, and code quality across the project.
app_feature_first_architecture
Feature-first architecture is a design pattern that organizes code by business features rather than technical layers. This approach promotes better maintainability, scalability, and team collaboration by keeping related functionality together and reducing coupling between different parts of the application.
best_practices
Advanced Best Practices covering Error Handling, Environment Variables, Performance, and Accessibility rules.