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-dossier)<a href="https://agentmods.dev/commands/peaky8linders/eu-ai-act-scanner/ai-act-dossier"><img src="https://agentmods.dev/badge/commands/peaky8linders/eu-ai-act-scanner/ai-act-dossier/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-dossier"><img src="https://agentmods.dev/badge/commands/peaky8linders/eu-ai-act-scanner/ai-act-dossier.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.00033 | $0.00413 |
| Opus 5.5 | $0.00013 | $0.00165 |
| Sonnet 5.5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
ai-act-dossier 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 8d 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-act-dossier
Produce a mathematically verifiable, tamper-evident compliance dossier binding the exact code state, git provenance, compliance scores, and statutory grounding.
Usage
/ai-act-dossier [PATH] [--out compliance-dossier.json]
Or via CLI:
python -m scanner.cli [PATH] --dossier compliance-dossier.json
What it binds
- SHA-256 File Manifest: Exact cryptographic digests of all scanned source files and configuration manifests.
- Git Provenance: Repository commit hash and active branch.
- Operator Roles: Inferred and declared operator roles (Provider vs Deployer).
- Compliance Scores: Dimension-by-dimension compliance scores and identified gaps.
- Statutory Grounding:
- Primary regulation: Regulation (EU) 2024/1689
- Amending enactment: Regulation (EU) 2026/1744 (Digital Omnibus on AI)
- Official CELEX reference:
02024R1689-20260727
- Cross-Framework Mappings: Readiness ratings across NIST AI RMF, ISO 42001, and GDPR.
- Applied Remediations: Tracked fixes applied via the remediation loop.
- Dossier Integrity Hash: A single cryptographic SHA-256 seal covering canonical dossier contents. Any modification to the dossier or underlying code breaks the signature.
Auditor / CI Gate Integration
Use the sealed dossier in CI/CD release pipelines to enforce conformity gates:
eu-ai-act-scan . --dossier release-dossier.json
If compliance scores fall below threshold or critical gaps are unresolved, the pipeline fails before code is deployed.
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.
- 8d ago First seen · 42 lines · 33 tokens per session scan A c7376ad96518
ai-act-dossier is a command published in the GitHub repository Peaky8linders/eu-ai-act-scanner (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 33 tokens to every session and 413 once invoked, about $0.0001 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-10-09.
Other commands, from other repositories
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.
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.
tcop
Generate a Technology Code of Practice (TCoP) review document for a UK Government technology project.
soa-generator
Generate ISO 27001 Statement of Applicability (SOA) with control selection justifications.
service-auditor-prep
Generate complete auditor-ready evidence package for SOC 2.