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/avoid-cleavage-in-prose)<a href="https://agentmods.dev/rules/prisma/orm/avoid-cleavage-in-prose"><img src="https://agentmods.dev/badge/rules/prisma/orm/avoid-cleavage-in-prose/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/avoid-cleavage-in-prose"><img src="https://agentmods.dev/badge/rules/prisma/orm/avoid-cleavage-in-prose.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.00273 | $0.00273 |
| Opus 5.5 | $0.00109 | $0.00109 |
| Sonnet 5.5 | $0.00055 | $0.00055 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
avoid-cleavage-in-prose 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:
- avoid-cleavage-in-prose — 100% identical, 0 lines differ
What it actually says
Avoid the word "cleavage" in prose
Don't use "cleavage" as a metaphor for a split, boundary, or division in any prose: docs, ADRs, specs, plans, READMEs, PR descriptions, commit messages, or code comments. The word is technically correct in the geological / structural sense but reads weirdly in technical writing because of its other common meaning, and the alternatives are clearer anyway.
Prefer the natural English alternative for the context:
| Instead of | Prefer |
|---|---|
| "the natural cleavage between X and Y" | "the natural split between X and Y" / "the natural distinction between X and Y" |
| "the cleavage is precise:" | "the split is precise:" / "the boundary is precise:" |
| "the cleavage between Project 1 and Project 2" | "the boundary between Project 1 and Project 2" |
| "predicate / non-predicate cleavage" | "predicate / non-predicate split" |
Use whichever of "split", "boundary", "distinction", or "divide" reads most naturally in the surrounding sentence.
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 · 20 lines · 273 tokens per session scan A 8500c45a3972
avoid-cleavage-in-prose is a cursor rule published in the GitHub repository prisma/orm (47,695 stars, last pushed yesterday), licensed Apache-2.0. It adds 273 tokens to every session, about $0.0011 per session on Opus 5.5. 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.
changeset
Write and verify package release changesets, registry changelog entries, and the PR’s managed auto-release choice. Use before deciding whether a package edit needs a changeset, including skipping one.
typescript-style
TypeScript style — prefer arrow functions and consistent callbacks.
release-ts-sdk
Release @aptos-labs/ts-sdk or @aptos-labs/confidential-asset — version bump, changelog stamp, release PR, then tag + GitHub Release that triggers NPM publish.
workflow
Workflow for openapi-to-cli.
security-archive
Socket.dev security data integration and security selectors.