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 commands/openehr/ai-plugins/publishgit clone --depth 1 https://github.com/openEHR/ai-pluginsWhat 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.00019 | $0.00479 |
| Opus 5 | $0.00010 | $0.00239 |
| Sonnet 5 | $0.00004 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
publish 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 2d 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.
What it actually says
Produce a local HTML preview of an openEHR specification component using the shared publishing
toolchain in specifications-AA_GLOBAL. This is the publish step described in the
openehr-specs:authoring skill — this command is the action wrapper. It builds a local preview
only; it does not tag, commit, or deploy a release (that is the governance skill / release process).
Arguments: $ARGUMENTS — the component abbreviation (e.g. RM, BASE, AM) and optionally a
single spec id to limit the build.
Do the following:
- Locate the publisher. Confirm a sibling
specifications-AA_GLOBALcheckout exists next to the component repo (the parent directory should contain bothspecifications-AA_GLOBAL/andspecifications-<component>/). If not, report what is missing and stop. - Run from the parent directory containing the
specifications-*repos. Prefer the script, fall back to Docker:./specifications-AA_GLOBAL/bin/spec_publish.sh -f -v $ARGUMENTS # or: docker run -u $(id -u):$(id -g) -v "$(pwd):/documents/" openehr/asciidoctor development $ARGUMENTS - Surface the result — report the generated HTML output location and any Asciidoctor warnings/errors (unresolved attributes, missing includes, missing images) verbatim, since those are exactly what a pre-publish check should catch.
- If the build fails, summarise the first actionable error and suggest the relevant skill
(
authoringfor include/attribute issues,xref-auditoragent for cross-reference failures).
Do not pass release flags (-r -t -q -l Release-N.N.N) — releasing is a governed process; use the
governance skill for that.
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.
- 2d ago First seen · 37 lines · 19 tokens per session scan A 9ec05c8027be
publish is a command published in the GitHub repository openEHR/ai-plugins (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 479 once invoked, about $0.0001 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 commands, from other repositories
planflow
Draft a plan and get it approved as an editable flowchart in the browser before executing.
sql-developer
Comprehensive SQL Server development assistance for T-SQL queries, stored procedures, performance tuning, and code review with Microsoft documentation verification.
powershell-developer
Comprehensive PowerShell development assistance for scripts, modules, GUIs, and Windows automation with Microsoft best practices verification.
rust-developer
Comprehensive Rust development assistance for systems programming, async applications, web services, and CLI tools with Rust documentation verification.
swift-developer
Comprehensive Swift development assistance for iOS/macOS apps, Swift packages, SwiftUI, Swift 6 concurrency, and code review with Apple documentation verification.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.