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 content-patternsgit 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/content-patterns)<a href="https://agentmods.dev/skills/openehr/ai-plugins/content-patterns"><img src="https://agentmods.dev/badge/skills/openehr/ai-plugins/content-patterns/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/content-patterns"><img src="https://agentmods.dev/badge/skills/openehr/ai-plugins/content-patterns.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.00116 | $0.00911 |
| Opus 5.5 | $0.00046 | $0.00364 |
| Sonnet 5.5 | $0.00023 | $0.00182 |
| Haiku 4.5 | $0.00012 | $0.00091 |
Grade A, and why
content-patterns 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 9d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
openEHR Specification Content Patterns
Apply these recurring prose patterns when writing new chapters or sections, to match the quality
and consistency of the existing specification library. They are derived from the openEHR
specification documents in the specifications-XX repositories (RM, AM, BASE, LANG, PROC, SM,
QUERY, CNF, TERM, ITS-*) and the shared infrastructure in specifications-AA_GLOBAL.
References
- Prose pattern catalog: see
references/prose-patterns.mdfor the full structure, AsciiDoc template, real example, and conventions for each pattern indexed below. - Cross-reference attribute guide: see
../authoring/references/cross-references.mdfor how to find and use{openehr_*}attributes when writing cross-references in spec prose. - Admonitions, code blocks, tables: see
../authoring/references/asciidoc-syntax.mdfor the syntax of a note, a code example, or a table in a chapter.
General Principles
- Formal register: third person, present tense, no contractions, no hedging.
- Declarative facts first: lead with what the model defines, not how the reader should interpret it.
- Design rationale where non-obvious: explain why, not just what.
- Ground every claim: reference RM classes, archetype paths, or external standards. Never invent identifiers; after drafting, dispatch the
identifier-groundingsubagent to verify each class, attribute, and function name against the published specifications. - Clinical examples: use concrete clinical scenarios to illustrate abstract model concepts.
Pattern Catalog
Pick the pattern that matches the section being written and read its detailed entry in
references/prose-patterns.md.
| # | Pattern | Use when writing… |
|---|---|---|
| 1 | Package/Chapter Overview | the opening of a chapter that describes a model package (opening paragraph → UML diagram → package/class enumeration) |
| 2 | Class/Concept Semantics | the prose for a class or major concept (purpose, typing, identification, structure, lifecycle, relationships) |
| 3 | Design Rationale | an explanation of why a non-obvious design choice was made (problem/requirement → chosen design → rejected alternatives) |
| 4 | Clinical/Practical Examples | a concrete clinical scenario that grounds an abstract model concept |
| 5 | Requirements Sections | an explicit numbered-requirements section preceding a design (common in Data Types, EHR IM) |
| 6 | Deprecated and TBD Markers | [.deprecated] or [.tbd] annotations for legacy or pending content |
| 7 | Figures and Diagrams in Context | any diagram — always introduced by text and followed by explanation |
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.
- 9d ago Changed · +5 tokens per session b0dcf65173f5
- 1mo ago First seen · 62 lines · 111 tokens per session scan A fe3ff33085b6
content-patterns is a skill published in the GitHub repository openEHR/ai-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 116 tokens to every session and 911 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
bottom-up-market-size
Size a market bottom-up from an Economic Mind market report and stress-test that number against independent sizing approaches - the headline size, the transparent per-company build (each player's revenue, share-in-market, in-market revenue, confidence and justification carried verbatim from the report), an explicit…
competitor-benchmarking
Benchmark a set of companies against each other on hard financials - a detailed per-year data table for each company (revenue, gross profit, EBITDA, EBIT, net income), plus a cross-company summary of size, growth and profitability, with every derived figure footnoted to its formula and inputs and every line attributed…
company-at-a-glance
Produce a rigorous, fully-sourced data snapshot of a single company - a detailed multi-year financial table (revenue, gross profit, EBITDA, EBIT, net income per year), computed margins and growth with every derived figure footnoted to its formula and inputs, plus web-sourced profile facts (founded, CEO, ownership…
getting-started
Orient a user to the Economic Mind plugin and connector - what it is, what data it draws on, which skills and connector tools are available, how to trigger them, and what to expect as the product grows. Use whenever the user is new to Economic Mind or asks what it is / what it can do / how to use it / how to get…
cognito
AWS Cognito user authentication and authorization service. Use when setting up user pools, configuring identity pools, implementing OAuth flows, managing user attributes, or integrating with social identity providers.
sns
AWS SNS notification service for pub/sub messaging. Use when creating topics, managing subscriptions, configuring message filtering, sending notifications, or setting up mobile push.