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/namespace-diagnostic-wordinggit 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/namespace-diagnostic-wording)<a href="https://agentmods.dev/rules/prisma/prisma-next/namespace-diagnostic-wording"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/namespace-diagnostic-wording.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.00102 | $0.00102 |
| Opus 5 | $0.00051 | $0.00051 |
| Sonnet 5 | $0.00020 | $0.00020 |
| Haiku 4.5 | $0.00010 | $0.00010 |
Grade A, and why
namespace-diagnostic-wording 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 4d 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
94% identical to namespace-diagnostic-wording — 2 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
Namespace diagnostic wording
When a PSL namespaced attribute is used but the namespace is unavailable in config, avoid phrasing like "namespace not composed".
Use clear user-facing wording such as:
- "unrecognized namespace"
- "namespace is not available"
Preferred guidance in messages:
- Name the namespace explicitly.
- Tell the user to add the corresponding extension pack to
extensionsinprisma-next.config.ts.
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.
- 4d ago First seen · 17 lines · 102 tokens per session scan A b43a8d5bbcf7
namespace-diagnostic-wording is a cursor rule published in the GitHub repository prisma/prisma-next (419 stars, last pushed 9d ago), licensed Apache-2.0. It adds 102 tokens to every session, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to namespace-diagnostic-wording, differing in 2 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.
family-instance-domain-actions
Family instance domain action implementation patterns.
import-validation
Import validation and package layering rules.
no-target-branches
Never branch on target - use adapters instead.