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/no-transient-project-ids-in-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.00650 | $0.00650 |
| Opus 5 | $0.00325 | $0.00325 |
| Sonnet 5 | $0.00130 | $0.00130 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
no-transient-project-ids-in-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 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.
This is a copy
100% identical to no-transient-project-ids-in-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.
How it starts
The opening of the file, as written. The whole thing — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
No transient project planning IDs in code
Source code, comments, test names, identifier strings, and hash fixtures must never reference transient project planning artefacts. Plans/specs are scratch documents deleted at close-out; encoding their IDs makes the code lie the moment the plan is rewritten or removed.
Transient (forbidden in code) — anything under projects/<x>/ or in a plan/spec/review doc:
- Task IDs (
T1.1,D7,M3.2), test-case IDs (TC-1,TC18), AC/FR/NFR IDs (AC1,FR2,NFR5), phase/round/checkpoint IDs (P3 R2,CKPT-2,M2 review) - Prose attributions to the plan ("out of scope per the spec", "sub-spec § 4", "deferred per project plan")
projects/<x>/...paths anywhere in source (incl. JSDoc@links and string literals)- Hash fixtures named after IDs (
'tc12-ext-contract')
Allowed (durable): Linear ticket IDs (TML-2408), ADR numbers (ADR 211), PR numbers (PR #494), permanent doc paths (docs/...), durable source paths (packages/..., test/..., examples/...).
How to comply
Describe the constraint or behaviour itself, not its plan row. Say "the runner skips ops with already-satisfied postchecks", not "see T3.4's postcheck-skip rule". Test names pin the property (it('runs both spaces in caller order')), not the coverage-table row. JSDoc cross-refs point at durable artefacts, never into projects/. Name fixtures/constants after their role ('mongo-ext-contract'), not the introducing test-case ID.
Before committing, scan your + diff for token-shaped IDs:
git diff --cached -- '*.ts' '*.tsx' '*.js' '*.mjs' | grep -E '^\+' \
| grep -oE '\b(T[0-9]+\.[0-9]+|TC-?[0-9]+|AC-?[0-9]+|FR[0-9]+|NFR[0-9]+|CKPT-[0-9]+|M[0-9]+\.[0-9]+|P[0-9]+ R[0-9]+)\b' | sort -u
Output should be empty. Freeform prose attributions ("per spec", "deferred per project plan") aren't token-catchable — scan manually. Companion to doc-maintenance.mdc, which covers the broader transient-artefact surface; this rule narrows to plan IDs left in source.
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 · 30 lines · 650 tokens per session scan A 22c1224b195b
no-transient-project-ids-in-code is a cursor rule published in the GitHub repository prisma/prisma-next (420 stars, last pushed 8d ago), licensed Apache-2.0. It adds 650 tokens to every session, about $0.0032 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to no-transient-project-ids-in-code, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
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.
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.
family-instance-domain-actions
Family instance domain action implementation patterns.