query-patterns

query-patterns is a cursor rule for Codex, Cursor from prisma/orm. It costs 0 tokens per session (205 once invoked), scanned A, original, Apache-2.0.

A set of coding rules for writing Prisma database queries in a Next.js project.

In plain words
What is it for?
Keeping database entry points small, wiring a PostgreSQL connection, and accessing Prisma tables and their columns explicitly.
Why use it?
It gives developers a consistent way to organize database access and refer to tables and columns, reducing confusing or conflicting query code.

Cursor rule for CodexCursor ✓ vendor

Written for Cursor: a Cursor rule (.mdc). Also seen: installed under .agents/ (shared by several agents).

Good fit Keeping database entry points small, wiring a PostgreSQL connection, and accessing Prisma tables and their columns explicitly.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/prisma/orm/query-patterns
About the project

Prisma ORM is a Node.js and TypeScript database toolkit that lets applications work with databases through a programming interface instead of writing every query directly in SQL. Developers use it with databases including PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB, and CockroachDB. The catalogue add-ons provide agent rules, skills, hooks, agents, and other workflows for using Prisma.

prisma/orm · 47,694 stars · on GitHub · prisma.io

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.

Clone the repo
git clone --depth 1 https://github.com/prisma/orm

Made for: Codex, 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 query-patterns

README.md
[![agentmods](https://agentmods.dev/badge/rules/prisma/orm/query-patterns/github.svg)](https://agentmods.dev/rules/prisma/orm/query-patterns)
Your own site
<a href="https://agentmods.dev/rules/prisma/orm/query-patterns"><img src="https://agentmods.dev/badge/rules/prisma/orm/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.

agentmods 80×15 button for query-patterns

Your own site · 80×15
<a href="https://agentmods.dev/rules/prisma/orm/query-patterns"><img src="https://agentmods.dev/badge/rules/prisma/orm/query-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 205 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
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.1 $0.00000 $0.00205
Opus 5.5 $0.00000 $0.00082
Sonnet 5.5 $0.00000 $0.00041
Haiku 4.5 $0.00000 $0.00020

Measured 1mo ago against content hash 843283aa6f07, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.agents/rules/query-patterns.mdc · 27 lines

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.ts that wires one postgres(...) call and keep query modules consuming db directly.
  • 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 tables frequently, extract locals:
    • const user = db.schema.tables.user
    • const cols = user.columns
  • .cursor/rules/sql-types-imports.mdc
  • .cursor/rules/validate-contract-usage.mdc
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. 1mo ago Changed 843283aa6f07
  2. 1mo ago First seen · 27 lines · 0 tokens per session scan A e91c4ad6efd6

Subscribe to this mod's changes

query-patterns is a cursor rule published in the GitHub repository prisma/orm (47,694 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 205 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-30.