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/prisma/prisma-nextWrote 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/prisma/prisma-next/query-patterns)<a href="https://agentmods.dev/rules/prisma/prisma-next/query-patterns"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/query-patterns/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/prisma/prisma-next/query-patterns"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/query-patterns.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.00204 |
| Opus 5.5 | $0.00000 | $0.00082 |
| Sonnet 5.5 | $0.00000 | $0.00041 |
| Haiku 4.5 | $0.00000 | $0.00020 |
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 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.
This is a copy
100% identical to query-patterns — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Query Patterns
This rulecard is intentionally short. For full examples, see docs/reference/query-patterns.md.
Keep query entrypoints small and explicit
- Prefer a small
db.tsthat wires onepostgres(...)call and keep query modules consumingdbdirectly. - Keep complex examples and walkthroughs in docs.
Prefer tables + table.columns.*
- Access columns via
db.schema.tables.user.columns.email(avoids conflicts with table properties). - If a file uses
tablesfrequently, extract locals:const user = db.schema.tables.userconst cols = user.columns
Related rules
.cursor/rules/sql-types-imports.mdc.cursor/rules/validate-contract-usage.mdc
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 · 27 lines · 0 tokens per session scan A e91c4ad6efd6
query-patterns is a cursor rule published in the GitHub repository prisma/prisma-next (414 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 204 tokens. A static security scan graded it A with 0 findings. It is 100% identical to query-patterns, differing in 2 lines, and is treated as a copy.
Other cursor rules, from other repositories
adapter-features
Database-specific features must be implemented in the specialized adapter only. Base adapters (postgres, mysql, etc.) must remain database-agnostic.
unit-tests-tdd
TDD required for behavior changes; ≥80% package coverage on touched packages; unit-test conventions.
planning-and-delegation
Plan every task first, parallelise independent work, and staff each task with the cheapest model that can do it well.
integration-tests
Human-readable integration test requests; helpers vs httptest; suites/ vs per-DB placement.
postgresql
PostgreSQL production rules. Safe migrations, parameterized queries, TIMESTAMPTZ, proper indexing strategy.
netlify-database-migration-from-extension
Switching to Netlify Database. Reference for the netlify-database skill.