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.
npx agentmods add rules/prisma/orm/no-backward-compatibilitygit clone --depth 1 https://github.com/prisma/ormWhat 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 | $0.00000 | $0.00291 |
| Opus 5 | $0.00000 | $0.00146 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
no-backward-compatibility 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 2d 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:
- no-backward-compatibility — 100% identical, 0 lines differ
What it actually says
No Backward Compatibility or Migration Paths
Rule
This project has no external consumers. Do NOT add:
- Backward compatibility code or APIs
- Migration paths or deprecation warnings
- Comments explaining "legacy" or "old" vs "new" approaches
- Test fixtures or examples showing old patterns alongside new ones
- Code comments documenting what changed or why it changed
What to Do Instead
Directly change the implementation:
- Remove old code entirely
- Update all references to use the new approach
- Update design docs to reflect the current state (not the transition)
- Update tests to only test the current approach
- Delete obsolete examples or fixtures
Rationale
Since this project has no external consumers, maintaining backward compatibility creates unnecessary complexity and technical debt. The codebase should reflect the current design, not preserve history of how it evolved.
Examples
Bad:
- Adding "legacy" codecs alongside new ones
- Keeping old test fixtures "for reference"
- Comments like "Legacy support - will be removed in future"
- Deprecation warnings or migration helpers
Good:
- Delete old code completely
- Update all references immediately
- Update design docs to show current state only
- Tests only exercise current patterns
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.
- 2d ago First seen · 44 lines · 0 tokens per session scan A 8d9d40c7c886
no-backward-compatibility is a cursor rule published in the GitHub repository prisma/orm (47,587 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 291 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
playwright-e2e
Playwright E2E testing configuration for AI agents.
react-components
Rules for writing React components in this project.
state-management
Rules for Redux state management.
server-patterns
Rules for server-side Express code.
project
AI Phone Agent — TypeScript voice backend (Twilio + Amazon Connect).
typescript-style
TypeScript style — prefer arrow functions and consistent callbacks.