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/girijashankarj/cursor-handbook/query-patternsgit clone --depth 1 https://github.com/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/query-patterns)<a href="https://agentmods.dev/rules/girijashankarj/cursor-handbook/query-patterns"><img src="https://agentmods.dev/badge/rules/girijashankarj/cursor-handbook/query-patterns.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00817 |
| Opus 5 | $0.00000 | $0.00409 |
| Sonnet 5 | $0.00000 | $0.00163 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
query-patterns 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 today.
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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Query Patterns
Absolute Rules
1. Soft Delete Only
- NEVER use
DELETE FROMstatements - ALWAYS use soft delete:
UPDATE table SET {{CONFIG.database.softDeleteField}} = false WHERE id = $1 - All queries MUST filter by
{{CONFIG.database.softDeleteField}} = trueunless explicitly recovering deleted records - Column naming convention:
{{CONFIG.database.naming}}
2. Parameterized Queries Only
-- CORRECT: Parameterized
SELECT * FROM orders WHERE id = $1 AND {{CONFIG.database.softDeleteField}} = true;
-- WRONG: String concatenation (SQL injection risk)
SELECT * FROM orders WHERE id = '${orderId}';
3. Required Columns
Every table MUST include:
| Column | Type | Description |
|---|---|---|
id |
UUID / BIGINT | Primary key |
{{CONFIG.database.timestampFields.created}} |
TIMESTAMP | Record creation time |
{{CONFIG.database.timestampFields.updated}} |
TIMESTAMP | Last update time |
{{CONFIG.database.softDeleteField}} |
BOOLEAN | Soft delete flag (default: true) |
Query Optimization
Indexing Strategy
- Index all foreign key columns
- Index columns used in WHERE clauses frequently
- Use composite indexes for multi-column queries
- Consider partial indexes for filtered queries
- Monitor slow query logs and add indexes accordingly
Pagination
- Prefer cursor-based pagination for large datasets
- Use
LIMIT+OFFSETonly for small datasets - Always include
ORDER BYwith pagination - Return
hasNextPageandcursorin pagination metadata
-- Cursor-based pagination (preferred)
SELECT * FROM orders
WHERE {{CONFIG.database.softDeleteField}} = true
AND {{CONFIG.database.timestampFields.created}} < $1
ORDER BY {{CONFIG.database.timestampFields.created}} DESC
LIMIT 20;
-- Offset pagination (simple cases only)
SELECT * FROM orders
WHERE {{CONFIG.database.softDeleteField}} = true
ORDER BY {{CONFIG.database.timestampFields.created}} DESC
LIMIT $1 OFFSET $2;
N+1 Prevention
- Use JOINs or batch queries instead of loops
- Use DataLoader pattern for GraphQL resolvers
- Preload associations when you know they'll be needed
- Monitor query counts per request in development
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.
- today First seen · 102 lines · 0 tokens per session scan A 59d4cea97205
query-patterns is a cursor rule published in the GitHub repository girijashankarj/cursor-handbook (30 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 817 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-09-03.
Other cursor rules, from other repositories
sql
Rules for SQL files (queries, migrations, stored procs).
graphstack
GraphStack v4.7.1 — Orchestrated, graph-first, GNAP-tracked AI development (cross-platform).
mysql-auto
This rule enforces MySQL-specific best practices to enhance readability, performance, security, and maintainability. It targets MySQL features (e.g., storage engines, character sets) and common pitfalls, and adds concrete guidance for schema design and creation.
t3-stack
T3 Stack: tRPC + Prisma + NextAuth integration patterns.
database-migrations
Database migrations: safety, rollbacks, zero-downtime.
prisma
Prisma: schema modeling, queries, migrations.