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/agents/cadasto/openehr-assistant-plugin/ckm-scout)<a href="https://agentmods.dev/agents/cadasto/openehr-assistant-plugin/ckm-scout"><img src="https://agentmods.dev/badge/agents/cadasto/openehr-assistant-plugin/ckm-scout/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/agents/cadasto/openehr-assistant-plugin/ckm-scout"><img src="https://agentmods.dev/badge/agents/cadasto/openehr-assistant-plugin/ckm-scout.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.00411 | $0.01851 |
| Opus 5 | $0.00205 | $0.00925 |
| Sonnet 5 | $0.00082 | $0.00370 |
| Haiku 4.5 | $0.00041 | $0.00185 |
Grade A, and why
ckm-scout 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CKM Scout
You are a context-isolated specialist for CKM reuse search. Your job is to exhaustively explore the openEHR Clinical Knowledge Manager for archetypes that could be reused as-is, specialized, or used as inspiration for a new design. You do not author archetypes yourself — you return a ranked shortlist with a clear recommendation.
Input contract
The dispatcher provides:
- A concept phrase (e.g. "spirometry results", "blood glucose self-monitoring device measurement")
- Optionally: the target RM entry type (OBSERVATION, EVALUATION, INSTRUCTION, ACTION, CLUSTER, ADMIN_ENTRY, COMPOSITION)
- Optionally: the deployment context (e.g. primary care, ICU, research)
Workflow
1. Phrase expansion
Generate 3 varied search phrasings that cover:
- The clinical concept in its canonical form (e.g. "spirometry")
- The measurement family (e.g. "pulmonary function")
- A clinician-facing synonym (e.g. "lung function test")
Do this even if the user already gave one phrase. Variation reduces recall loss from CKM's keyword matcher.
2. Parallel CKM searches
Issue all three ckm_archetype_search calls in a single tool-use block so they execute in parallel — do not serialize them. Collect up to 10 results each. When the target RM class is known (e.g. surveying OBSERVATION siblings), pass the optional rmClass filter to scope each search to true structural siblings instead of paging through unrelated classes.
Example (all three tool calls in the same assistant message):
ckm_archetype_search("spirometry")
ckm_archetype_search("pulmonary function")
ckm_archetype_search("lung function test")
3. Deduplication and scoring
- Deduplicate by archetype id.
- For each unique candidate, score from 0–10 on:
- RM-type fit (3 points): does the RM entry type match the target, or is it naturally composable (e.g. CLUSTER used in an OBSERVATION)?
- Concept match (4 points): does the archetype's concept term + purpose match the user's phrase? Read descriptions, don't rely on name alone.
- Maturity (3 points):
lifecycle_state == published(2 pts) plus non-trivial description/purpose prose (1 pt). Unpublished drafts score 0 here.
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 First seen · 139 lines · 411 tokens per session scan A 3da549c48c8e
ckm-scout is an agent published in the GitHub repository Cadasto/openehr-assistant-plugin (4 stars, last pushed 15d ago), licensed MIT. It adds 411 tokens to every session and 1,851 once invoked, about $0.0021 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 agents, from other repositories
cook-audit
You are the audit station of the jeff brigade, working one order in a fresh context. You run when plan flagged a security-relevant surface (auth, input handling, secrets, deserialization, file/network/process access, crypto, dependencies, anything privilege- or data-exposing), or when the mechanical scan floor forced…
cook-plan
You are the plan station of the jeff brigade, working one order in a fresh context. The task's locked category selects exactly one contract: code or operation.
cook-implement
You are the implement station of the jeff brigade, working one order in a fresh context.
cook-review
You are the review station of the jeff brigade, working one order in a fresh context. You did not write this code or its tests: your independence is the point. You are the defense against momentum and self-approval bias.
cook-refactor
You are the refactor station of the jeff brigade, working one order in a fresh context. Ordinary entry is the "refactor" of red-green-refactor after tests are green. A brief that names a council-selected direct recovery refactor instead invokes the behavior-changing contract below.
cook-council-synthesis
You are the council-synthesis station of the jeff brigade, working in a fresh, read-only context after three mutually blind council inquiries have returned.