standard-sql-best-practices

standard-sql-best-practices is a cursor rule for Cursor from Im-Hal-9K/capacities-mcp. It costs 0 tokens per session (332 once invoked), scanned A, original, from a forked repository, MIT.

A set of SQL rules for writing safer and more stable database queries and transactions. SQL is the language commonly used to read and change data in relational databases.

In plain words
What is it for?
Reviewing SQL queries and database changes involving indexes, constraints, pagination, locking, transaction isolation, selected columns, and conditions that can use indexes.
Why use it?
It helps avoid problems such as slow pagination, incorrect concurrent updates, weak data validation, unstable performance, and poorly controlled transactions.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/im-hal-9k/capacities-mcp/standard-sql-best-practices
Clone the repo
git clone --depth 1 https://github.com/Im-Hal-9K/capacities-mcp

Made for: Cursor.

Wrote 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.

agentmods badge for standard-sql-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/rules/im-hal-9k/capacities-mcp/standard-sql-best-practices.svg)](https://agentmods.dev/rules/im-hal-9k/capacities-mcp/standard-sql-best-practices)
Your own site
<a href="https://agentmods.dev/rules/im-hal-9k/capacities-mcp/standard-sql-best-practices"><img src="https://agentmods.dev/badge/rules/im-hal-9k/capacities-mcp/standard-sql-best-practices.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 332 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin fork From a forked repository.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00332
Opus 5 $0.00000 $0.00166
Sonnet 5 $0.00000 $0.00066
Haiku 4.5 $0.00000 $0.00033

Measured 5d ago against content hash d3199cc835c5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

standard-sql-best-practices 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 5d 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.

.cursor/rules/packmind/standard-sql-best-practices.mdc · 19 lines

What it actually says

Standard: SQL Best Practices

This standard covers high-impact SQL practices for security, concurrency, transactional correctness, performance stability, and operability. It targets non-obvious pitfalls around isolation, locking, ... :

  • Avoid OFFSET pagination on large tables; use keyset pagination with a stable, unique ordering predicate.
  • Create composite indexes matching leading equality filters then ordering; avoid indexing only low-selectivity columns or mismatched column order.
  • Enforce data invariants with constraints; prefer CHECK, FOREIGN KEY, NOT NULL, and UNIQUE over application-only validation.
  • Keep predicates sargable; avoid applying functions to indexed columns in WHERE and JOIN conditions, and rewrite to range predicates.
  • Lock rows with SELECT ... FOR UPDATE when reading values that will be updated in the same transaction; avoid read-then-update without locks.
  • Select only required columns in production queries; avoid SELECT * in application-facing SQL and stable interfaces like views.
  • Set transaction isolation explicitly at transaction start for any multi-statement write flow; do not rely on session or database defaults.
  • Use parameter placeholders for all external values; pass lists via typed arrays or table-valued parameters, not string-built IN clauses.
  • Use window functions for “top N per group” and latest-row selection; avoid correlated subqueries with LIMIT per row.
  • Write DDL migrations as idempotent steps using IF EXISTS/IF NOT EXISTS and guarded backfills; avoid non-repeatable migrations.

Full standard is available here for further request: SQL Best Practices

Changes

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.

  1. 5d ago First seen · 19 lines · 332 tokens per session scan A d3199cc835c5

Subscribe to this mod's changes

standard-sql-best-practices is a cursor rule published in the GitHub repository Im-Hal-9K/capacities-mcp (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 332 tokens. A static security scan graded it A with 0 findings. It comes from a forked repository.