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/prisma-next/adr-examples-must-match-codegit clone --depth 1 https://github.com/prisma/prisma-nextWhat 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.00261 |
| Opus 5 | $0.00000 | $0.00130 |
| Sonnet 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 yesterday.
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 adr-examples-must-match-code — 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
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.
- yesterday 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/prisma-next (421 stars, last pushed 7d ago), 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. It is 100% identical to adr-examples-must-match-code, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
directory-layout
Directory layout rules for SQL family vs concrete targets.
family-instance-domain-actions
Family instance domain action implementation patterns.
import-validation
Import validation and package layering rules.