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/n0rvyn/cursor-rules/012-evidence-requirementsgit clone --depth 1 https://github.com/n0rvyn/cursor-rulesWrote 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/n0rvyn/cursor-rules/012-evidence-requirements)<a href="https://agentmods.dev/rules/n0rvyn/cursor-rules/012-evidence-requirements"><img src="https://agentmods.dev/badge/rules/n0rvyn/cursor-rules/012-evidence-requirements.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.1 | $0.01593 | $0.01593 |
| Opus 5 | $0.00796 | $0.00796 |
| Sonnet 5 | $0.00319 | $0.00319 |
| Haiku 4.5 | $0.00159 | $0.00159 |
Grade A, and why
012-evidence-requirements 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 203 lines · 1,593 tokens per session scan A 2b1323ffa8fb
012-evidence-requirements is a cursor rule published in the GitHub repository n0rvyn/cursor-rules (2 stars, last pushed 9mo ago), with no licence file. It adds 1,593 tokens to every session, about $0.0080 per session on Opus 5. 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-31.
Other cursor rules, from other repositories
standard-agent-quality
Применять в VERIFY фазе каждой задачи. Определяет метрики успеха (linter=0, cross-check, challenge), границы (guardrails), feedback loop. Target: задачи без переделок >80%, повторные ошибки <10%.
dependency-check
Dependency management and security vulnerability scanning guidelines for Node.js/npm projects.
cursorrules
This project uses Spec-Driven Protocol (SDP) v0.9.0.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.