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/inboxpraveen/Minimize-Cursor-CostWrote 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/inboxpraveen/minimize-cursor-cost/sql)<a href="https://agentmods.dev/rules/inboxpraveen/minimize-cursor-cost/sql"><img src="https://agentmods.dev/badge/rules/inboxpraveen/minimize-cursor-cost/sql/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/inboxpraveen/minimize-cursor-cost/sql"><img src="https://agentmods.dev/badge/rules/inboxpraveen/minimize-cursor-cost/sql.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.00383 |
| Opus 5.5 | $0.00000 | $0.00153 |
| Sonnet 5.5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
sql 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 Rules
Style
- Match existing case convention: keywords UPPERCASE vs lowercase, identifiers snake_case vs camelCase.
- Match existing indentation and trailing-comma style.
- Don't reformat unrelated lines.
Output
- For migrations: write only the new migration file's contents. Don't reprint old ones.
- For query edits: show only the changed clause(s) when possible. If the full query is needed, show it complete (queries don't usefully diff in pieces).
Migrations
- Never edit a migration that has been applied to production. Add a new migration.
- Match the existing migration tool's idioms (Alembic, Prisma, Knex, Flyway, Liquibase, raw SQL).
- Always include a reversible/down step if siblings have one.
- Don't drop columns/tables in the same migration that adds replacements — split into two.
Queries
- Don't add
SELECT *to existing code that names columns. - Don't add new indexes speculatively — call them out as a suggestion instead.
- Don't change
JOINorder or types (INNER↔LEFT) unless that's the bug. - For aggregations, match existing alias style.
Performance
- Don't add
EXPLAIN ANALYZEoutput to context — summarize it. - Don't suggest denormalization or schema redesign as a side-effect of a query fix.
Never
- Don't use vendor-specific features (Postgres
JSONB, MySQLON DUPLICATE KEY) if the codebase targets multiple DBs. - Don't add stored procedures / triggers unless the codebase already uses them.
- Don't change collation, character set, or timezone settings while doing a feature task.
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 · 38 lines · 0 tokens per session scan A ee5f5a43b932
sql is a cursor rule published in the GitHub repository inboxpraveen/Minimize-Cursor-Cost (10 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 383 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
query-patterns
Database query patterns, optimization, and safety rules. Apply when writing or editing queries.
migration-rules
Database migration patterns and safety rules. Apply when creating or editing migrations.
schema-design
Database schema design conventions and standards. Apply when designing schema or migrations.
integration-testing
Integration testing patterns and database test setup.
30-database-postgres
PostgreSQL and persistence rules.
postgres
Postgres roof: parameterized SQL, forward-only migrations, measured indexes. Index only.