governance-documentation

governance-documentation is a skill for Claude Code from lexbeam-software/eu-ai-governance-plugin. It costs 59 tokens per session (771 once invoked), scanned A, original, Apache-2.0.

A guide for creating and organising records that show how an AI system meets EU AI Act governance requirements.

In plain words
What is it for?
Use it to prepare technical documentation, logs, quality records, declarations, registration records, monitoring files, incident files, and evidence indexes.
Why use it?
It helps connect each required record to the right legal rule, owner, source, approval, retention period, and system version.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the eu-ai-governance plugin — 6 skills, 6 commands, 1 MCP server shipped together

Good fit Use it to prepare technical documentation, logs, quality records, declarations, registration records, monitoring files, incident files, and evidence indexes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lexbeam-software/eu-ai-governance-plugin/governance-documentation
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.

Any agent
npx skills add lexbeam-software/eu-ai-governance-plugin --skill governance-documentation
Clone the repo
git clone --depth 1 https://github.com/lexbeam-software/eu-ai-governance-plugin

Made for: Claude Code.

Or install eu-ai-governance, the plugin that ships this one along with the rest of its 6 skills, 6 commands, 1 MCP server.

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 governance-documentation

README.md
[![agentmods](https://agentmods.dev/badge/skills/lexbeam-software/eu-ai-governance-plugin/governance-documentation/github.svg)](https://agentmods.dev/skills/lexbeam-software/eu-ai-governance-plugin/governance-documentation)
Your own site
<a href="https://agentmods.dev/skills/lexbeam-software/eu-ai-governance-plugin/governance-documentation"><img src="https://agentmods.dev/badge/skills/lexbeam-software/eu-ai-governance-plugin/governance-documentation/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 governance-documentation

Your own site · 80×15
<a href="https://agentmods.dev/skills/lexbeam-software/eu-ai-governance-plugin/governance-documentation"><img src="https://agentmods.dev/badge/skills/lexbeam-software/eu-ai-governance-plugin/governance-documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 771 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.00771
Opus 5 $0.00030 $0.00385
Sonnet 5 $0.00012 $0.00154
Haiku 4.5 $0.00006 $0.00077

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

Security

Grade A, and why

governance-documentation 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 9d 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.

skills/governance-documentation/SKILL.md · 54 lines

How it starts

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

Build governance documentation

Create an evidence map before drafting prose. Identify the system, version, intended purpose, actors, classification, applicable articles, owner, retention rule, source, approval, and change history for every artifact.

Follow LEGAL-SOURCE-PROTOCOL.md and AI-ACT-DECISION-MAP.md. Use euaiact_annex_iv_checklist, euaiact_get_obligations, and the versioned summary and official URL returned by euaiact_get_article when the Lexbeam EU AI Act MCP is available. Read the official full text for exact wording.

Map evidence to the correct anchor

  • Article 11 and Annex IV: provider technical documentation before market placement or putting into service; keep it current.
  • Article 12: technical capability for automatic logging over the system lifetime.
  • Article 13: information and instructions supplied to deployers.
  • Article 14: designed human-oversight measures.
  • Article 17: provider quality management system.
  • Article 18: provider documentation keeping for 10 years after market placement or putting into service, subject to the article’s scope and sector rules.
  • Article 19: provider retention of automatically generated logs under its control for an appropriate period of at least six months, unless other law provides otherwise.
  • Article 26(6): deployer retention of logs under its control on the same minimum-period logic.
  • Article 43: conformity assessment.
  • Article 47: EU declaration of conformity.
  • Article 48: CE marking.
  • Article 49: registration, including Article 49(2) for an Article 6(3) non-high-risk determination.
  • Article 72: provider post-market monitoring.
  • Article 73: provider serious-incident reporting.

Never label Article 18 as conformity assessment or Article 19 as the EU declaration of conformity.

Build an evidence index

For each requirement record:

Field Required content
Requirement Exact article, paragraph, point, or Annex item
Actor Provider, deployer, or other role
Applicability Applies, does not apply with reason, or not established
Artifact File, system record, log, decision, or external evidence
Version and date Effective version, approval date, review date
Owner and approver Accountable role and recorded approval
Integrity Repository, checksum or immutable record where proportionate
Retention Legal or organisational basis and disposal trigger
Gap Missing, stale, conflicting, inaccessible, or complete

Read the full file on GitHub · 54 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. 9d ago First seen · 54 lines · 59 tokens per session scan A 0325e16a8d80

Subscribe to this mod's changes

governance-documentation 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 59 tokens to every session and 771 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.