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 skills add lexbeam-software/eu-ai-governance-plugin --skill dpia-aigit clone --depth 1 https://github.com/lexbeam-software/eu-ai-governance-pluginWrote 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/skills/lexbeam-software/eu-ai-governance-plugin/dpia-ai)<a href="https://agentmods.dev/skills/lexbeam-software/eu-ai-governance-plugin/dpia-ai"><img src="https://agentmods.dev/badge/skills/lexbeam-software/eu-ai-governance-plugin/dpia-ai/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/skills/lexbeam-software/eu-ai-governance-plugin/dpia-ai"><img src="https://agentmods.dev/badge/skills/lexbeam-software/eu-ai-governance-plugin/dpia-ai.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.00066 | $0.00765 |
| Opus 5 | $0.00033 | $0.00382 |
| Sonnet 5 | $0.00013 | $0.00153 |
| Haiku 4.5 | $0.00007 | $0.00076 |
Grade A, and why
dpia-ai 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 10d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run an AI DPIA
Support the controller’s assessment; do not claim approval or legal advice. The controller remains accountable. If a DPO is designated, seek and document the DPO’s advice under GDPR Article 35(2); the GDPR does not make DPO approval a universal legal condition.
Follow LEGAL-SOURCE-PROTOCOL.md for legal conclusions and source notes.
Determine whether a DPIA is required
Apply GDPR Article 35 to the specific processing. Consider:
- systematic and extensive evaluation based on automated processing, including profiling, where decisions have legal or similarly significant effects
- large-scale special-category or criminal-offence data
- systematic monitoring of publicly accessible areas on a large scale
- relevant supervisory-authority lists and EDPB/WP29 guidance
Label the familiar “two or more criteria” approach as guidance, not statutory text. Record the trigger analysis even when the conclusion is that no DPIA is required.
When decisive facts are missing, issue a provisional trigger decision and list the facts needed to finalise it. Do not pause without giving the user the safe analysis available from supplied facts.
Describe the processing
Document controller, processors, joint controllers, purpose, users, affected persons, data sources and categories, model and system flow, recipients, transfers, storage, retention, automated effects, human intervention, and lifecycle changes. Use a data-flow diagram when it clarifies the processing.
Assess necessity and proportionality
Test purpose specification, legal basis, data minimisation, accuracy, retention, transparency, rights handling, Article 22 where relevant, alternatives, human intervention, and processor controls. Do not use an AI Act classification as a GDPR lawful basis.
Assess risks to people
Describe concrete harms, affected groups, likelihood, severity, uncertainty, and controls. Include discrimination, proxy effects, erroneous decisions, opacity, manipulation, security, data leakage, function creep, exclusion, chilling effects, feedback loops, and contestability where relevant.
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.
- 10d ago First seen · 53 lines · 66 tokens per session scan A f13d152ca0bf
dpia-ai is a skill published in the GitHub repository lexbeam-software/eu-ai-governance-plugin (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 66 tokens to every session and 765 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 skills, from other repositories
air-blackbox-sales-agent
AIR Blackbox's autonomous sales prospecting agent. Finds Python AI projects on GitHub that need EU AI Act compliance, identifies the right person to contact (CEO, CTO, lead maintainer), runs a free compliance scan, and drafts personalized outreach emails that convert to engagement. The sales flow: free scan as the…
interpret-results
Interprets AIR Blackbox scan results and maps findings to specific EU AI Act articles, recitals, and remediation steps. Use when the user has scan output and wants to understand what to fix, why it matters, or how to prioritize.
compliance-scan
Scans a Python AI project for EU AI Act compliance gaps using AIR Blackbox. Use when the user asks to check compliance, scan their code, audit their AI project, or mentions EU AI Act, Articles 9-15, or compliance checking.
runtime-admissibility-review
Determines whether a specific AI-agent action, output, recommendation, or proposed commitment remains admissible for execution or institutional reliance under current authority, delegated scope, evidence, facts, policy, risk, escalation, and revocation conditions. Use this Skill before an enterprise or regulated AI…
agent-authority-charter-builder-arkadiy-miteiko
Creates an Agent Authority Charter for enterprise or regulated AI agents before deployment. Use this Skill when a user needs to define what an AI agent is allowed to do, who delegated authority to it, what actions are permitted or prohibited, when human approval is required, what evidence must be preserved, and how…
complyedge-eu-ai-act-runtime-deny
Runtime deny for EU AI Act Article 5 and Article 50 on this prompt or output via ComplyEdge TrustLint MCP. Use when the user wants agent I/O compliance enforcement, not system classification, FRIA forms, or C2PA watermarking.