Borrowing it
Nothing to install: this file belongs to CSOAI-ORG/ai-incident-reporting-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/CSOAI-ORG/ai-incident-reporting-mcp/main/.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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" 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.5 | $0.00062 | $0.00062 |
| Sonnet 5.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 1mo 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.
- 1mo 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 19d ago), licensed MIT. It adds 156 tokens to every session, about $0.0006 per session on Opus 5.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
legalithm-eu-ai-act
EU AI Act compliance guidance — cite Regulation (EU) 2024/1689, never claim instant compliance.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.