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.
git clone --depth 1 https://github.com/Peaky8linders/eu-ai-act-scannerWrote 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/commands/peaky8linders/eu-ai-act-scanner/ai-act-incidents)<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.
<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>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.00059 | $0.01239 |
| Opus 5 | $0.00030 | $0.00620 |
| Sonnet 5 | $0.00012 | $0.00248 |
| Haiku 4.5 | $0.00006 | $0.00124 |
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.
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
- Dimension id — e.g.
--limit N(optional) — number of incidents to return. Defaults to 5.--real-world-only(optional) — restrict tocorpus="real-world"incidents (excludes research-demonstrated).
Behaviour
-
Normalise
$1to determine lookup type (dimension / article / threat). -
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) -
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
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.
- 11d ago First seen · 97 lines · 59 tokens per session scan A f4e411abde58
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.
Other commands, from other repositories
discover
Discover runtime AI components and static AI dependencies with AIR Blackbox.
replay
Replay recorded AI traces to detect behavioral drift between model versions.
evidence
Export a signed compliance evidence package as JSON or PDF for regulatory handoff.
comply
Run a full EU AI Act compliance scan on your Python AI project.
status
Check the current governance status for your session, including your plan, remaining capacity, and whether the governance layer is operating normally.
audit
Generate a structured audit report for the current session or a specified time range. The report summarises every governed action, lists any blocked requests, and provides a compliance-ready summary you can download or share.