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 reviewgit 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/review)<a href="https://agentmods.dev/skills/openehr/ai-plugins/review"><img src="https://agentmods.dev/badge/skills/openehr/ai-plugins/review/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/review"><img src="https://agentmods.dev/badge/skills/openehr/ai-plugins/review.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.00099 | $0.01274 |
| Opus 5.5 | $0.00040 | $0.00510 |
| Sonnet 5.5 | $0.00020 | $0.00255 |
| Haiku 4.5 | $0.00010 | $0.00127 |
Grade A, and why
review 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
openEHR Specification Document Review
Review an openEHR specification document against the conventions used across all
specifications-XX repositories.
Review Process
- Identify the target — determine the spec directory (e.g.,
docs/ehr/) and read the key files - Run each check category — work through the full catalog in
references/check-catalog.md, collecting findings as ERROR, WARNING, or INFO - Present findings grouped by category with
file:linereferences - Propose fixes for ERRORs and WARNINGs (only modify files if asked)
Inline Review or Subagent
Choose by scope:
- Review inline for one chapter, one file, or a few files. Apply only the checks those files allow and state which checks were skipped.
- Dispatch the
spec-reviewersubagent for a whole spec directory, a whole component, or a pre-release review. It runs this same catalog in an isolated context and returns only the findings table. - Dispatch the
xref-auditorsubagent when the concern is links. XREF-01 to XREF-04 only check that attributes are defined and links are styled; the subagent also resolves<<anchor>>targets and, with web access, cross-spec#fragmentanchors. - Dispatch the
identifier-groundingsubagent to verify that class, attribute, and function names exist in the published specifications. No check in this catalog does this.
Pre-Review: File Discovery
Read these files for the target spec:
master.adoc— main entry pointmanifest_vars.adoc— per-document variablesmaster00-amendment_record.adoc— amendment recordmaster01-preface.adoc— preface- Every chapter file in scope (
master02-*.adoc, etc.); search all chapters for the pattern checks (FIG, ADOC, XREF, CONTENT) rather than sampling - The component's
manifest.json(in the repo root)
Also reference the shared infrastructure in the sibling specifications-AA_GLOBAL checkout (if it is absent, skip XREF-01 and say so):
specifications-AA_GLOBAL/docs/boilerplate/global_vars.adocspecifications-AA_GLOBAL/docs/references/reference_definitions.adoc
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 · +18 lines · +11 tokens per session 3d55bebc1fd8
- 1mo ago First seen · 79 lines · 88 tokens per session scan A f20f8c0d3213
review is a skill published in the GitHub repository openEHR/ai-plugins (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 99 tokens to every session and 1,274 once invoked, about $0.0004 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
board-deck-builder
Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes.
security-architecture-review
Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practices around it. Use this to review an architecture or pull request for security, set secure coding standards, choose or tune SAST and DAST tooling, assess a…
code-review
Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. Use this before merging, when asked to review a diff or pull request, when review feedback has arrived and needs acting on, or when feedback seems wrong and needs a…
okf-open-knowledge-format
Create, validate, and enrich Open Knowledge Format (OKF) bundles — the open spec for representing organizational knowledge as markdown files with YAML frontmatter. Use when the user mentions 'OKF', 'Open Knowledge Format', 'knowledge bundle', 'OKF bundle', 'create a knowledge base for agents', 'validate OKF', 'convert…
security-specialist
Runs security audits on codebases — full scans, diff reviews, threat models, vulnerability triage, remediation guidance, and finding tracking. Activate when the user says "security scan", "audit this repo", "review this PR for security", "threat model", "triage vulnerabilities", "fix this vuln", or "track findings".
agent-plugin-eval
Audit, score, and compare repositories containing portable Agent Plugins against the official Agent Plugins specification. Use when asked to review a plugin repo, check plugin.json or mcp.json conformance, assess bundled skills and MCP servers, produce an evidence-cited 0–100 plugin scorecard, identify release…