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 agentmods add skills/openehr/ai-plugins/governancenpx skills add openEHR/ai-plugins --skill governancegit clone --depth 1 https://github.com/openEHR/ai-pluginsWrote 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/openehr/ai-plugins/governance)<a href="https://agentmods.dev/skills/openehr/ai-plugins/governance"><img src="https://agentmods.dev/badge/skills/openehr/ai-plugins/governance.svg" alt="Measured on agentmods" 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 | $0.00113 | $0.01553 |
| Opus 5 | $0.00056 | $0.00776 |
| Sonnet 5 | $0.00023 | $0.00311 |
| Haiku 4.5 | $0.00011 | $0.00155 |
Grade A, and why
governance 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 4d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
openEHR Specification Governance
This skill covers the change process, release management, and lifecycle governance for openEHR specifications. It is based on the official governance documents at specifications.openehr.org/governance.
Related Skills
- authoring — document scaffolding, repo layout, boilerplate structure
- amendment-record — detailed amendment record authoring conventions
- review — pre-release quality review of spec documents
Specification Lifecycle States
Every specification follows a formal lifecycle:
Planning → Development → Trial → Stable
↓
Paused → Retired
| State | Duration | Format | Versioning | Change Management |
|---|---|---|---|---|
| Planning | 6 months max | Wiki | 0.y.z | Informal |
| Development | 18 months max | Wiki | 0.y.z | Optional CRs |
| Trial | 2 years max | HTML + computable | x.y.z | Formal CRs |
| Stable | Unbounded | HTML + computable | x.y.z | Formal CRs |
| Paused | Unbounded | HTML + computable | paused | CRs only for state changes |
| Retired | Unbounded | Frozen version | n/a | None |
The Specifications Editorial Committee (SEC) reviews promotion criteria three months before target dates. Unmet criteria may trigger a single three-month extension; subsequent failure results in retirement.
The spec_status field in manifest.json and manifest_vars.adoc tracks this state.
Versioning
openEHR uses three-part semantic versioning (x.y.z):
- Patch (z): Error corrections and minor additions that do not change semantics
- Minor (y): Significant additions that do not change existing semantics
- Major (x): Semantic changes requiring potential software upgrades or data migration
Documentation-only corrections (typos, clarifications) receive a revision number update without triggering a new release number.
Artifact Types
Problem Reports (PRs)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 178 lines · 113 tokens per session scan A b355ba5564a2
governance is a skill published in the GitHub repository openEHR/ai-plugins (3 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 113 tokens to every session and 1,553 once invoked, about $0.0006 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
ai-ml-governance
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory…
c2pa-sign
Embed C2PA provenance manifests in AI-generated assets — the machine-readable AI disclosure EU AI Act Article 50 expects (enforceable since 2 Aug 2026), plus the human-approval record for the Article 50(4) exemption. Triggers on "/c2pa-sign", "sign this asset", "provenance", "content credentials", "AI disclosure"…
project-forget
GDPR Art 17 delete. Tombstone projects/{slug}/, schedule physical deletion in 30 days. Use /forget-project . Cannot be undone after 30d.
state-fee-lookup
Use to look up sales tax rate, doc fee cap, title fee, registration fee, and trade-in credit eligibility for any of 50 US states + DC. Returns the fees in seconds rather than searching DMV websites. Triggers include "what's the doc fee in X", "NJ sales tax rate", "Texas DMV fees", "州的税率", "doc fee cap", "trade-in…
cloud-security
Cloud security best practices for AWS, GCP, and Azure. Use when securing cloud infrastructure, configuring IAM, hardening S3 buckets, setting up VPC security, compliance (SOC2, ISO 27001), or auditing cloud resources for misconfigurations.
healthy-skill
Converts contracts to redlined drafts. Use when: 'redline this contract', 'compare contract versions'.