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.
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/ormWrote 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/orm/adr-examples-must-match-code)<a href="https://agentmods.dev/rules/prisma/orm/adr-examples-must-match-code"><img src="https://agentmods.dev/badge/rules/prisma/orm/adr-examples-must-match-code/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/orm/adr-examples-must-match-code"><img src="https://agentmods.dev/badge/rules/prisma/orm/adr-examples-must-match-code.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.00261 |
| Opus 5.5 | $0.00000 | $0.00104 |
| Sonnet 5.5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
adr-examples-must-match-code 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- adr-examples-must-match-code — 100% identical, 0 lines differ
What it actually says
ADR examples must match real code
When adding or editing an ADR, every reference to the codebase — code examples and prose mentions of type names, function names, field names, diagnostic-code strings, and file paths — must match the shipped source, not a draft or a memory of the API:
- Prefer examples that are copy/pasteable and reflect the current API.
- Avoid inventing fluent helper syntax unless it already exists in the codebase.
- Verify each cited symbol, field, diagnostic code, and file path by searching the source before documenting it — don’t trust the name you remember or the name a spec used.
- Close-out ADRs are drawn from a project spec that predates implementation. Field and symbol names routinely get renamed during the slices, so the spec is the least reliable naming source by the time the ADR is written. Treat the spec as intent; confirm every name against the merged code.
- Resolve every relative link from the ADR’s own directory depth (ADRs live one level deeper than
projects/), so../counts are easy to get wrong.
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 · 18 lines · 0 tokens per session scan A dce8c306a851
adr-examples-must-match-code is a cursor rule published in the GitHub repository prisma/orm (47,693 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 261 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.
Other cursor rules, from other repositories
prisma
Prisma database patterns and conventions for Next.js and TypeScript projects.
typescript-style
TypeScript style — prefer arrow functions and consistent callbacks.
drizzle-patterns
Drizzle ORM patterns and database conventions.
react-typescript
Rules for writing frontend code at PostHog (mostly React + Typescript with Kea).
windsurfrules
Node.js ESM + EloquentJS ORM + PostgreSQL/MongoDB + Express/Fastify.
code-validation-workflow
Code validation workflow (format, lint, test, coverage, typecheck).