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-target-branchesgit 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.01088 |
| Opus 5 | $0.00000 | $0.00544 |
| Sonnet 5 | $0.00000 | $0.00218 |
| Haiku 4.5 | $0.00000 | $0.00109 |
Grade A, and why
no-target-branches 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-target-branches — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
No Target-Specific Branches
CRITICAL: Never name a target in target-agnostic code. This covers two forms of the same mistake: branching on a target value, and embedding target-named constants, helpers, or data in framework/core packages. Target-specific logic and target-specific facts belong in adapters and target packages.
❌ WRONG: Branch on target in core packages
function canonicalizeColumnType(scalar: string, target: string): string {
if (target === 'postgres') {
const scalarMap: Record<string, string> = {
int4: 'pg/int4@1',
text: 'pg/text@1',
};
return scalarMap[scalar] ?? scalar;
}
return scalar;
}
✅ CORRECT: Put target-specific logic behind an adapter interface
interface Adapter {
canonicalizeType(scalar: string): string;
}
class PostgresAdapter implements Adapter {
canonicalizeType(scalar: string): string {
const scalarMap: Record<string, string> = {
int4: 'pg/int4@1',
text: 'pg/text@1',
};
return scalarMap[scalar] ?? scalar;
}
}
Named-target constants and data are the same violation
The branch is the obvious form. The subtler form is a target-agnostic package that names a target in a constant, a helper name, or static data — even with no if in sight. A POSTGRES_DEFAULT_NAMESPACE_ID constant or a defaultNamespaceIdForSqlTarget() helper sitting in the framework core is just a branch that has been pre-evaluated: the framework now knows a Postgres-specific fact.
❌ WRONG: Target-named constant / helper in a target-agnostic package
// in packages/1-framework/** (target-agnostic)
export const POSTGRES_DEFAULT_NAMESPACE_ID = 'public';
export function defaultNamespaceIdForSqlTarget(targetId: string): string {
return targetId === 'postgres' ? 'public' : '__unbound__';
}
✅ CORRECT: The target declares the fact on its descriptor; the framework reads it generically
// in the target package's descriptor (static data the target owns)
const postgresDescriptorMeta = {
// …
defaultNamespaceId: 'public',
};
// in the target-agnostic consumer — reads the fact, never names the target
const defaultNamespaceId = target.defaultNamespaceId;
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 · 107 lines · 0 tokens per session scan A 570091e14bf9
no-target-branches 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 1,088 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.