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-writing)<a href="https://agentmods.dev/rules/prisma/orm/adr-writing"><img src="https://agentmods.dev/badge/rules/prisma/orm/adr-writing/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-writing"><img src="https://agentmods.dev/badge/rules/prisma/orm/adr-writing.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.00480 |
| Opus 5.5 | $0.00000 | $0.00192 |
| Sonnet 5.5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
adr-writing 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-writing — 88% identical, 1 lines differ
What it actually says
- Lead with the decision and a grounding example. Open with a representative code/usage sample and the decision itself, then build up why → how → consequences, and put alternatives considered last. Don't front-load context/problem/rejected designs — a reader should see what the decision is before the information being made irrelevant. (Context still belongs in the doc; it just doesn't lead.)
- ADRs are long-lived — no transient references. No PR numbers, and no "before this refactor / earlier implementation / as-shipped / what we used to do" preceding-state framing. The shape you replaced is a legitimate alternative considered, stated timelessly — not narrated as a project event. (Ticket / milestone / task IDs are already banned in ADRs by
no-transient-project-ids-in-code.mdc.) - Keep responsibility splits explicit (e.g. adapter lowering vs codec encode/decode vs driver transport/normalization)
- If an ADR discusses capabilities, follow
.cursor/rules/capabilities-ownership.mdcfor wording - If you need to describe sequencing (order of operations), keep it short and place it near the responsibilities/decision; avoid long procedural sections that read out-of-place
- Use fenced code blocks for SQL (
```sql) and TS (```ts); avoid nested backticks inside inline code - Worked examples should be end-to-end and make it obvious which layer owns each step (lane, adapter, codec, driver, runtime)
- If the decision instantiates a structural pattern recorded in
docs/architecture docs/patterns/, link forward to the pattern entry from the ADR (existing ADRs are not retroactively edited) - Maintain the ADR in the PR that changes the decision. When a decision evolves mid-project, update its ADR (and add supersession notes to any ADR it displaces) in the same PR — not in a follow-up. An ADR whose examples drift from the shipped surface violates
adr-examples-must-match-code.mdcand misleads longer than it informs.
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 · 17 lines · 0 tokens per session scan A 6053d442ad9f
adr-writing 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 480 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).