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/jonafrank/cursor-multi-model-config/05-compliancegit clone --depth 1 https://github.com/jonafrank/cursor-multi-model-configWrote 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/jonafrank/cursor-multi-model-config/05-compliance)<a href="https://agentmods.dev/rules/jonafrank/cursor-multi-model-config/05-compliance"><img src="https://agentmods.dev/badge/rules/jonafrank/cursor-multi-model-config/05-compliance.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.00013 | $0.00343 |
| Opus 5 | $0.00006 | $0.00171 |
| Sonnet 5 | $0.00003 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
05-compliance 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.
What it actually says
Compliance Mode
This rule activates for review, validation, and compliance checking tasks.
When This Applies
- Code review
- Security audits
- Best practices validation
- Standards compliance checking
- Accessibility reviews
- Performance reviews
Model Recommendation
Check .cursor/model-profiles/current-profile.json for the compliance model.
Typical models for compliance:
claude-4.5-opus-high(completeness/default profile)claude-4.5-haiku(cost_minimized/fallback profile)
Compliance Guidelines
- Be thorough: Check all relevant aspects
- Prioritize issues: Critical > Major > Minor
- Cite standards: Reference specific rules/guidelines
- Provide fixes: Don't just identify problems
- Acknowledge positives: Note what's done well
Review Categories
Security
- Input validation
- Authentication/authorization
- Data exposure risks
- Injection vulnerabilities
Code Quality
- Error handling
- Edge cases
- Type safety
- Documentation
Performance
- Inefficient patterns
- Memory leaks
- Unnecessary operations
Standards
- Naming conventions
- Code style
- Project-specific rules
Output Format
For compliance tasks:
| Severity | Issue | Location | Recommendation |
|---|---|---|---|
| Critical | ... | ... | ... |
| Major | ... | ... | ... |
| Minor | ... | ... | ... |
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 · 69 lines · 13 tokens per session scan A 73bac0d3135d
05-compliance is a cursor rule published in the GitHub repository jonafrank/cursor-multi-model-config (5 stars, last pushed 8mo ago), licensed MIT. It adds 13 tokens to every session and 343 once invoked, about $0.0001 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
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.