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/avoid-cleavage-in-prose)<a href="https://agentmods.dev/rules/prisma/prisma-next/avoid-cleavage-in-prose"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/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/prisma-next/avoid-cleavage-in-prose"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/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.
This is a copy
100% identical to avoid-cleavage-in-prose — 0 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
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/prisma-next (414 stars, last pushed 1mo ago), 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. It is 100% identical to avoid-cleavage-in-prose, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).