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.
git clone --depth 1 https://github.com/Cadasto/openehr-assistant-pluginWrote 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/rules/cadasto/openehr-assistant-plugin/openehr-context)<a href="https://agentmods.dev/rules/cadasto/openehr-assistant-plugin/openehr-context"><img src="https://agentmods.dev/badge/rules/cadasto/openehr-assistant-plugin/openehr-context/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/rules/cadasto/openehr-assistant-plugin/openehr-context"><img src="https://agentmods.dev/badge/rules/cadasto/openehr-assistant-plugin/openehr-context.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.00000 | $0.00278 |
| Opus 5.5 | $0.00000 | $0.00111 |
| Sonnet 5.5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
openehr-context 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 1mo 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
openEHR context
When the workspace involves openEHR (archetypes, templates, AQL, ADL, CKM, compositions, OPT, terminology):
- Guide-first: Load relevant implementation guides from the openEHR Assistant MCP server (
guide_search/guide_get) before creating or editing archetypes, templates, AQL, or composition formats. - MCP tools: Use
mcp__openehr-assistant__*tools for CKM search, guide access, terminology, type specs, ADL idioms, and curated examples as needed. - Slash invocations: Prefer the openEHR Assistant commands and user-invocable skills when they fit the task (e.g.
/ckm-search,/openehr-explain,/semantic-diff,/archetype-impact); they encode guide-first workflows.
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.
- 1mo ago First seen · 15 lines · 0 tokens per session scan A 0660eb2396b7
openehr-context is a cursor rule published in the GitHub repository Cadasto/openehr-assistant-plugin (5 stars, last pushed 28d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 278 tokens. 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 cursor rules, from other repositories
battle-tested-engineer
Battle-tested engineering judgment for code, refactors, tests, and frontend UI. Ultra-terse caveman style during code work.
generated-file-patterns
Auto-generated and binary file patterns excluded from PR review.
risk-factors
Risk scoring factor definitions and weights for PR review dispatch.
sensitive-paths
Sensitive file path patterns that increase risk score during PR review.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.