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/ai-incident-reporting-mcp/cursorrulesgit clone --depth 1 https://github.com/CSOAI-ORG/ai-incident-reporting-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/ai-incident-reporting-mcp/cursorrules)<a href="https://agentmods.dev/rules/csoai-org/ai-incident-reporting-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/csoai-org/ai-incident-reporting-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.1 | $0.00156 | $0.00156 |
| Opus 5 | $0.00078 | $0.00078 |
| Sonnet 5 | $0.00031 | $0.00031 |
| Haiku 4.5 | $0.00016 | $0.00016 |
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 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.
What it actually says
AI Incident Reporting MCP - Auto-trigger Rules
When the user asks about AI incident reporting, serious incident classification, EU AI Act Article 73, OECD AI Incident Monitor (AIM), or multi-regime incident routing, use ai-incident-reporting-mcp tools:
- classify_incident: Multi-regime classification (EU AI Act + DORA + NIS2 + GDPR breach)
- generate_report: Draft an incident notification per applicable regime
- routing_check: Determine which authorities must be notified and within what SLA
Install: pip install ai-incident-reporting-mcp
Single incident may trigger 3-4 parallel reporting obligations (provider authority + national CSIRT + DPA + sectoral). This MCP routes correctly.
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 · 12 lines · 156 tokens per session scan A 3bbcd87f89ca
cursorrules is a cursor rule published in the GitHub repository CSOAI-ORG/ai-incident-reporting-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 156 tokens to every session, about $0.0008 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 meok watermark attest, use meok-watermark-attest-mcp tools: getdeadlinestatus, classifyobligations, generatedisclosuretext, auditcontentpipeline, signwatermarkattestation.
cursorrules
When the user asks about agent-to-agent audit trails, immutable A2A logging, DORA/NIS2/EU AI Act audit requirements, or attestation-signed bundle export, use agent-audit-logger-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 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.
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.