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/as-contract-cast-smellgit 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/as-contract-cast-smell)<a href="https://agentmods.dev/rules/prisma/prisma-next/as-contract-cast-smell"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/as-contract-cast-smell.svg" alt="Measured on agentmods" 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 | $0.00941 | $0.00941 |
| Opus 5 | $0.00470 | $0.00470 |
| Sonnet 5 | $0.00188 | $0.00188 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
as-contract-cast-smell 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 5d 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 as-contract-cast-smell — 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
as Contract casts are a serializer-bypass smell
The smell
// ❌ WRONG — bypasses the family ContractSerializer seam
const contract = JSON.parse(raw) as Contract;
const contract = JSON.parse(raw) as Contract<SqlStorage>;
Casting JSON.parse(...) directly to Contract looks innocent in review — Contract is a structural interface, so the cast compiles cleanly. The runtime cost is silent: structural arktype validation, IR-class hydration, and polymorphic-slot discriminator dispatch are all skipped, and the program proceeds with a JSON envelope masquerading as a hydrated Contract. That hides the class of bugs TML-2536 surfaced (untagged storage.types entries that crashed downstream consumers).
The fix
Route every on-disk contract read through the family ContractSerializer seam:
// ✅ CORRECT — crosses the family deserializer seam
const raw = await readFile(path, 'utf-8');
const familyInstance = config.family.create(createControlStack(config));
const contract = familyInstance.deserializeContract(JSON.parse(raw) as unknown);
The as unknown half is the explicit JSON.parse → unknown step — JSON.parse is typed any in TS today and the unknown narrowing makes the deserializer call the only place where structural assumptions get checked. This matches the pattern documented in typed-contract-in-tests.mdc.
In production code that already has a Contract value validated upstream and just needs to pass it along, no cast is needed — the existing typing carries through.
Lint scope
The lint:no-contract-cast workspace script enforces the cast-keyword variant of this smell (as Contract and as Contract<...> outside the allowlist). Structural-assignment variants — e.g. const c: Contract = JSON.parse(raw), or passing a JSON.parse'd value into a function whose parameter is annotated Contract — are NOT lint-enforced, because TypeScript's structural typing makes complete coverage arbitrarily hard. The seam-of-record is the lint plus the convention: every on-disk contract read must be a familyInstance.deserializeContract(...) call at the read site, reviewed in PR.
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.
- 5d ago First seen · 65 lines · 941 tokens per session scan A 660dc9523a7f
as-contract-cast-smell is a cursor rule published in the GitHub repository prisma/prisma-next (419 stars, last pushed 10d ago), licensed Apache-2.0. It adds 941 tokens to every session, about $0.0047 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to as-contract-cast-smell, 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-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.
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.