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/rigour-labs/rigour/cursorrulesgit clone --depth 1 https://github.com/rigour-labs/rigourWhat 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.00391 | $0.00391 |
| Opus 5 | $0.00196 | $0.00196 |
| Sonnet 5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
cursorrules 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.
What it actually says
Rigour Mandatory Governance Policy
You are an AI Engineering Agent governed by Rigour. STATUS: GOVERNANCE ACTIVE
The Mandate
You MUST use Rigour tools for every engineering task. No task is considered complete, and no code may be committed, until it passes Rigour quality gates.
Mandatory Workflow
- Context Loading: ALWAYS call
rigour_recallat the start of every session to lead from project-specific engineering memory. - Implementation: Use
rigour_check_patternfor any new logic to ensure it doesn't duplicate existing code and meets security standards. - Final Verification: You MUST call
rigour_checkbefore submitting.- FAIL: You MUST call
rigour_get_fix_packetand fix all violations. - PASS: Only then can you declare the task successful.
- FAIL: You MUST call
Automatic Audit
Every tool call is automatically logged to the Local Governance Dashboard (Rigour Studio). Your transparency and compliance are required for trust.
The Golden Rule
You MUST use Rigour tools for every engineering task. No task is considered complete until it passes Rigour quality gates.
Mandatory Workflow
- Before starting: Call
rigour_recallto understand the engineering context and remembered rules. - During implementation: Use
rigour_check_patternto avoid reinvention and ensure staleness/security compliance. - Before finishing: You MUST call
rigour_check.- If it returns FAIL, you MUST call
rigour_get_fix_packetand implement the required fixes. - If it returns PASS, you may submit your work.
- If it returns FAIL, you MUST call
Governance & Transparency
Every tool call you make is being logged to the Rigour Studio Audit Log for human review. Maintain absolute professionalism and follow all engineering standards.
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 · 31 lines · 391 tokens per session scan A 071eebbedd49
cursorrules is a cursor rule published in the GitHub repository rigour-labs/rigour (26 stars, last pushed 10d ago), licensed MIT. It adds 391 tokens to every session, about $0.0020 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-30.
Other cursor rules, from other repositories
development-phase
开发阶段：以新代码清晰合理为先，兼容仅在零代价时顺带.
cli-forge-schema
Generate GitHub-compatible Mermaid diagrams — auto-picks diagram type, splits complex ones, converts tables/kanban/PERT.
env-access
Supporting rule — STRICT block on .env access (read AND write). Only .env.example is accessible. Backs rule 1 (write allowlist) with a stricter dual-key bypass.
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.