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 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/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/openehr/ai-plugins/governance"><img src="https://agentmods.dev/badge/skills/openehr/ai-plugins/governance.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.00124 | $0.01727 |
| Opus 5.5 | $0.00050 | $0.00691 |
| Sonnet 5.5 | $0.00025 | $0.00345 |
| Haiku 4.5 | $0.00012 | $0.00173 |
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 19d 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 — 177 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 (the
spec-reviewerandxref-auditorsubagents run it across a whole spec or component)
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 carries this state in upper case (for example DEVELOPMENT, TRIAL, STABLE, PAUSED, RETIRED; the full list is in ../authoring/references/manifest-spec-entry.md). Keep both copies identical. To promote a spec, confirm that the SEC has approved the promotion, then set spec_status identically in both files.
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
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.
- 19d ago Changed · -1 lines · +11 tokens per session bd957d36b0c0
- 1mo 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 3d ago), licensed Apache-2.0. It adds 124 tokens to every session and 1,727 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
contract-and-proposal-writer
Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs. Structured Markdown output with docx conversion instructions. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions. Not a substitute for legal counsel — use as strong starting…
general-counsel-advisor
General Counsel advisory for startups: contract review (MSA, SaaS, NDA, DPA, employment), IP strategy, term sheet decoding, and regulatory landscape mapping. Use when reviewing any contract or term sheet, deciding when to engage outside counsel, defining IP strategy, evaluating regulatory exposure (HIPAA, GDPR, FDA…
ma-playbook
M&A strategy for acquiring companies or being acquired. Due diligence, valuation, integration, and deal structure. Use when evaluating acquisitions, preparing for acquisition, M&A due diligence, integration planning, or deal negotiation.
chief-legal-and-risk-officer
Owns legal, contracts, intellectual property, regulatory compliance, privacy, security governance, enterprise risk, and audit readiness. Use this to review a contract or commitment, assess regulatory or privacy exposure, evaluate an IP or licensing question, judge the risk in a business decision, prepare for an audit…
chief-human-resources-officer
Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations. Use this to design or restructure a team, plan hiring, write a role or leveling definition, handle a performance or compensation question, diagnose why a team is underperforming for non-technical…
capital-structure-and-covenants
Decides how the business is financed and what that financing then requires of it — debt versus equity, weighted average cost of capital as a hurdle rate, how much leverage cash flow can carry, and the financial, affirmative and negative covenants, definitions, test dates and cure rights that come attached. Use this to…