Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/openEHR/ai-pluginsnpx agentmods add skills/openehr/ai-plugins/bmm-authoringWrote 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/bmm-authoring)<a href="https://agentmods.dev/skills/openehr/ai-plugins/bmm-authoring"><img src="https://agentmods.dev/badge/skills/openehr/ai-plugins/bmm-authoring/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/bmm-authoring"><img src="https://agentmods.dev/badge/skills/openehr/ai-plugins/bmm-authoring.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.00153 | $0.02965 |
| Opus 5.5 | $0.00061 | $0.01186 |
| Sonnet 5.5 | $0.00031 | $0.00593 |
| Haiku 4.5 | $0.00015 | $0.00297 |
Grade A, and why
bmm-authoring 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 7d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
openEHR BMM Schema Authoring (P_BMM JSON)
A component's BMM schema, computable/BMM/openehr_<component>_<release>.bmm.json, is the source of
truth for its classes. The class tables and diagrams in its documents are generated from it (see
class-generation), and
specifications-ITS-BMM republishes it as JSON,
ODIN and YAML. Change the model here, and only here.
- Format reference:
${CLAUDE_SKILL_DIR}/references/p-bmm-json.md. Before editing, read the sections for the constructs involved (its Contents lists header, packages, every class, property, type and function kind, what the tables show, and the spec features the toolchain does not read). - Worked example:
${CLAUDE_SKILL_DIR}/assets/openehr_demo_0.1.0.bmm.json, one of each common construct. - Checker:
${CLAUDE_SKILL_DIR}/scripts/check_bmm.py(Python 3.8+, standard library only, read-only).
Where It Applies
Only in a component repo. Check manifest.json id (or the directory name specifications-<id>)
first. In the ITS-XML, ITS-BMM, ITS-JSON and ITS-REST repos, create and edit no BMM schema. Say that
the repo holds no model of its own, and make the change in the component's
specifications-<COMPONENT>/computable/BMM/ instead. ITS-BMM copies its JSON from there and
generates its ODIN and YAML with its own make generate. Running the read-only checker on a file
there is fine.
Related Skills
- class-generation: regenerate and place the class tables after a change
- authoring: the chapter
include::lines for a new or removed class - amendment-record: the entry for a change to published specification text
- governance: releases, and the lifecycle state a schema header names
- content-patterns: the prose around classes, which the tables do not carry
- scaffold: writes a new repository's schema, the image's bundled copy or an empty one
(
/openehr-specs:scaffold)
Why the Checker Comes Before the Render
What ships with it
3 files 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.
- 7d ago First seen · 165 lines · 153 tokens per session scan A b7f595607c93
bmm-authoring is a skill published in the GitHub repository openEHR/ai-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 153 tokens to every session and 2,965 once invoked, about $0.0006 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-10-10.
Other skills, from other repositories
bootstrap-xcode-workspace
Create, adopt, extend, and align one Swift product workspace with app, extension, package, and service components under one permanent Xcode entrypoint.
bootstrap-solution
Bootstrap or guide a reproducible .NET solution with explicit F# or C# language choice, SDK selection, project layout, test project setup, and initial validation commands.
build-kotlin-android
Implement Kotlin-first Android app or library changes, including activities, fragments, services, receivers, Compose UI, XML/AppCompat UI, AndroidX, lifecycle-aware coroutines, state, persistence touchpoints, resources, accessibility labels, navigation touchpoints, tests, lint, and validation while preserving repo…
build-csharp-project
Build or modify idiomatic C# .NET projects using nullable-aware APIs, records/classes, async/task behavior, analyzer conventions, tests, and repo-local validation.
build-fsharp-project
Build or modify idiomatic F# .NET projects using explicit modules, domain types, functional data flow, file ordering, async/task interop, tests, and repo-local validation.
fsharp-csharp-interop
Design and maintain explicit F# and C# boundaries in mixed .NET solutions, including project references, public API shape, async/task interop, nullability, options, records, and package-facing contracts.