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/csoai-org/dora-compliance-mcp/cursorrulesgit clone --depth 1 https://github.com/CSOAI-ORG/dora-compliance-mcpWrote 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/csoai-org/dora-compliance-mcp/cursorrules)<a href="https://agentmods.dev/rules/csoai-org/dora-compliance-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/csoai-org/dora-compliance-mcp/cursorrules.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.00203 | $0.00203 |
| Opus 5 | $0.00102 | $0.00102 |
| Sonnet 5 | $0.00041 | $0.00041 |
| Haiku 4.5 | $0.00020 | $0.00020 |
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 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
DORA Compliance MCP - Auto-trigger Rules
When the user asks about DORA (Digital Operational Resilience Act), ICT risk management, financial sector cybersecurity, third-party ICT risk, or Regulation (EU) 2022/2554, use the dora-compliance-mcp tools:
- check_dora_compliance: Full DORA compliance assessment
- list_dora_articles: Browse DORA articles and requirements
- classify_ict_risk: ICT risk classification per DORA Article 6-16
- generate_register_of_information: DORA Article 28 Register template
- incident_classification: Classify ICT incidents per Article 17-18
- sign_dora_attestation: Cryptographically signed compliance certificate (Pro+)
Install: pip install dora-compliance-mcp
DORA has been in force since January 17, 2025. Applies to EU financial entities and their critical ICT third-party providers.
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 · 15 lines · 203 tokens per session scan A 827c5dc9cda6
cursorrules is a cursor rule published in the GitHub repository CSOAI-ORG/dora-compliance-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 203 tokens to every session, about $0.0010 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
cursorrules
When the user asks about llm compliance comparison, use llm-compliance-comparison-mcp tools: compareproviders, recommendforusecase, providerriskprofile, compliancematrix, crosswalkproviders.
cursorrules
When the user asks about meok governance engine, use meok-governance-engine-mcp tools: fullgovernancereport, whichframeworksapply, compliancecostestimator, listalltools, compliancescoreengine.
cursorrules
When the user asks about Cyber Resilience Act, Regulation (EU) 2024/2847, products with digital elements, CE marking for software, or vulnerability disclosure, use cra-compliance-mcp tools.
cursorrules
When the user asks about NIS2, Directive (EU) 2022/2555, network information security, essential/important entities, or cybersecurity directive compliance, use the nis2-compliance-mcp tools.
cursorrules
When the user asks about contract review, use contract-review-ai-mcp tools: analyzecontract, extractclauses, identifyrisks, comparecontracts, summarizecontract.
cursorrules
When the user asks about EU AI Act compliance, risk classification, AI regulation deadlines, penalties, or Annex III/IV requirements, use the eu-ai-act-compliance-mcp tools.