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/amendgit 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.00025 | $0.00574 |
| Opus 5 | $0.00013 | $0.00287 |
| Sonnet 5 | $0.00005 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
amend 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 yesterday.
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
Add a new entry to the amendment record of the openEHR specification being worked on. The
amendment-record conventions (anchors, Jira keys, release boundaries, version-bump rules) are
defined in the openehr-specs:amendment-record skill and its references/conventions.md — follow
them; this command is the action wrapper.
Arguments: $ARGUMENTS — the Jira CR/PR reference(s) and a short description of the change
(e.g. SPECRM-142 — add tags to LOCATABLE; addresses SPECPR-401).
Do the following:
- Locate the amendment record. Find the relevant
master00-amendment_record.adoc. If the spec directory is ambiguous, ask which spec; if a single spec is in scope, use it. - Read it to learn the current top issue number, format (
[cols=...]), and raiser style. - Classify the version bump from the change description (patch = corrections/clarifications, minor = new content/sections, major = restructuring) per the amendment-record skill's rubric. If unclear, state your assumption and proceed.
- Optionally inspect the diff for context:
git -C <repo> diff(andgit status) to see what actually changed, so the entry describes it accurately. - Insert the new entry at the top of the table (immediately after the header row):
- Move the
[[latest_issue]]and[[latest_issue_date]]anchors onto this new entry. - Format Jira references as
{spec_tickets}/SPECXX-NN[SPECXX-NN^]: <description>; link any PRs it addresses ("Addresses {spec_tickets}/SPECPR-NN[SPECPR-NN^]"). - Use today's date in
dd Mon yyyyform (ask if the date is uncertain — do not guess a date). - If this is the first entry after a release, add the
4+^h|*XX Release N.N.N*boundary row below it.
- Move the
- Show the diff of the change and stop. Do not publish or commit.
Keep the Details cell concise and specific — state what changed, not why (the Jira ticket holds the rationale).
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.
- yesterday First seen · 36 lines · 25 tokens per session scan A 7220e3950aff
amend is a command published in the GitHub repository openEHR/ai-plugins (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 574 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.
README
Git workflow and quality assurance commands for the claude-skills repository.