ai-act-incidents

ai-act-incidents is a command for Claude Code from Peaky8linders/eu-ai-act-scanner. It costs 59 tokens per session (1,239 once invoked), scanned A, original, Apache-2.0.

A command that looks up documented security incidents and research examples connected to an AI risk, EU AI Act article, or threat category. The EU AI Act is a European law governing certain uses of artificial intelligence.

In plain words
What is it for?
Use it to investigate topics such as prompt injection, data theft, model inversion, privilege escalation, logging, or human oversight, with optional limits and real-world-only filtering.
Why use it?
It provides evidence for security assessments instead of relying only on abstract threat descriptions, and connects incidents to several security frameworks.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: positional $N argument.

Good fit Use it to investigate topics such as prompt injection, data theft, model inversion, privilege escalation, logging, or human oversight, with optional limits and real-world-only filtering.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/peaky8linders/eu-ai-act-scanner/ai-act-incidents
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Peaky8linders/eu-ai-act-scanner

Made for: Claude Code.

Wrote 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.

agentmods badge for ai-act-incidents

README.md
[![agentmods](https://agentmods.dev/badge/commands/peaky8linders/eu-ai-act-scanner/ai-act-incidents/github.svg)](https://agentmods.dev/commands/peaky8linders/eu-ai-act-scanner/ai-act-incidents)
Your own site
<a href="https://agentmods.dev/commands/peaky8linders/eu-ai-act-scanner/ai-act-incidents"><img src="https://agentmods.dev/badge/commands/peaky8linders/eu-ai-act-scanner/ai-act-incidents/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.

agentmods 80×15 button for ai-act-incidents

Your own site · 80×15
<a href="https://agentmods.dev/commands/peaky8linders/eu-ai-act-scanner/ai-act-incidents"><img src="https://agentmods.dev/badge/commands/peaky8linders/eu-ai-act-scanner/ai-act-incidents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,239 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00059 $0.01239
Opus 5 $0.00030 $0.00620
Sonnet 5 $0.00012 $0.00248
Haiku 4.5 $0.00006 $0.00124

Measured 11d ago against content hash f4e411abde58, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

ai-act-incidents 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 11d 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.

commands/ai-act-incidents.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/ai-act-incidents

Ground scanner gaps in documented incident history. Returns real-world and research-demonstrated incidents that map to the requested dimension, article, or threat category, with cross-framework taxonomy mappings (OWASP LLM Top 10 2025, OWASP Agentic AI Top 10, NIST AI RMF, MITRE ATLAS) and published mitigations.

Arguments

  • $1 (required) — lookup key. Three accepted forms:
    • Dimension id — e.g. security, risk_mgmt, human_oversight, logging, lethal_trifecta
    • Article id — e.g. art9, art15, art72. Accepts the same normalisation as /ai-act-article: art9, Art. 9, 9, ART9.
    • Threat-category id — e.g. prompt_injection, data_exfiltration, model_inversion, privilege_escalation
  • --limit N (optional) — number of incidents to return. Defaults to 5.
  • --real-world-only (optional) — restrict to corpus="real-world" incidents (excludes research-demonstrated).

Behaviour

  1. Normalise $1 to determine lookup type (dimension / article / threat).

  2. Call the appropriate corpus API:

    from scanner import incidents_for_dimension, incidents_for_article
    from scanner.incident_grounding import incidents_for_threat
    
    # dimension
    incidents = incidents_for_dimension("security", limit=5)
    
    # article
    incidents = incidents_for_article("art15", limit=5)
    
    # threat
    incidents = incidents_for_threat("prompt_injection", limit=5)
    
  3. Present results in this structure:

    # Incidents for: security (Art. 15 — accuracy, robustness, cybersecurity)
    
    Dataset: GenAI & Agentic AI Security Incidents (emmanuelgjr/genai-incidents, CC-BY-4.0)
    Showing 5 of N matching reviewed incidents.
    
    ## INC-03441 — LLM agent exfiltrates CRM records via prompt injection (2024)
    Corpus: real-world | Severity: critical
    OWASP LLM: LLM01, LLM06 | OWASP ASI: ASI01
    MITRE ATLAS: AML.T0051 (LLM Prompt Injection), AML.T0054 (LLM Jailbreak)
    NIST AI RMF: MEASURE-2.7, MANAGE-4.1
    
    Description: [one-sentence summary from incident.description]
    
    Mitigations:
    - Insert a HITL gate before write actions on sensitive data stores
    - Sanitize and validate all inputs from untrusted channels before passing to the LLM
    - Apply output filtering to detect and block exfiltration patterns
    
    EU AI Act relevance:
    - Art. 15(4): prompt-injection resilience is an explicit cybersecurity obligation
    - Art. 9(2)(b): this incident class constitutes foreseeable misuse for any agent with
      external-input access and data-store read capability
    

Read the full file on GitHub · 97 lines

Changes

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.

  1. 11d ago First seen · 97 lines · 59 tokens per session scan A f4e411abde58

Subscribe to this mod's changes

ai-act-incidents is a command published in the GitHub repository Peaky8linders/eu-ai-act-scanner (5 stars, last pushed 4d ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,239 once invoked, about $0.0003 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.