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 Cadasto/openehr-assistant-plugin --skill demographic-modelinggit 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/skills/cadasto/openehr-assistant-plugin/demographic-modeling)<a href="https://agentmods.dev/skills/cadasto/openehr-assistant-plugin/demographic-modeling"><img src="https://agentmods.dev/badge/skills/cadasto/openehr-assistant-plugin/demographic-modeling/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/cadasto/openehr-assistant-plugin/demographic-modeling"><img src="https://agentmods.dev/badge/skills/cadasto/openehr-assistant-plugin/demographic-modeling.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.00126 | $0.01849 |
| Opus 5 | $0.00063 | $0.00924 |
| Sonnet 5 | $0.00025 | $0.00370 |
| Haiku 4.5 | $0.00013 | $0.00185 |
Grade A, and why
demographic-modeling 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 10d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Demographic Modeling
The RM detail in the steps below is a working summary. The
specs/rm-demographicguide loaded in Step 1 is authoritative — if they disagree, follow the guide (or confirm againsttype_specification_get).
Conflict Resolution
When guides conflict, apply this priority (highest first):
- Rules and structural constraints
- Privacy and separation principles
- Anti-patterns
- Principles and examples
- Convenience
Step 1: Load Guides (MANDATORY)
Before any demographic modeling work, load the authoritative guides:
guide_get("openehr://guides/specs/rm-demographic")
guide_get("openehr://guides/archetypes/principles")
Load additional guides as needed:
guide_get("openehr://guides/specs/rm-ehr")— for EHR/demographic separation context and cross-referencing patterns
Step 2: Clarify Use Case
Before designing, gather requirements:
- Entity types: Which PARTY subtypes are needed — PERSON, ORGANISATION, GROUP, AGENT?
- Roles: What roles do parties play? What capabilities and time validity apply?
- Relationships: What relationships exist between parties? What is the directionality?
- Deployment context: Is this a standalone demographic service, a PMI wrapper, or embedded within an EHR system?
- Privacy requirements: What level of PARTY_SELF identification is appropriate for the deployment?
Step 3: Research Before Creating
Before designing new demographic archetypes, ALWAYS search CKM first:
ckm_archetype_search("person")
ckm_archetype_search("organisation")
ckm_archetype_search("party identity")
Reuse-first principle: If a suitable demographic archetype exists, use it. Only create new archetypes when no existing archetype covers the concept. If a close match exists, consider specialization instead.
Use ckm_archetype_get to retrieve and review candidate archetypes in full before deciding. For a deeper reuse survey across varied phrasings (demographic concepts are easy to phrase several ways), dispatch the ckm-scout agent — it runs parallel searches and returns a ranked reuse/specialize/new recommendation without filling the main context with raw hits.
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.
- 10d ago First seen · 183 lines · 126 tokens per session scan A 06c65eaee286
demographic-modeling is a skill published in the GitHub repository Cadasto/openehr-assistant-plugin (4 stars, last pushed 15d ago), licensed MIT. It adds 126 tokens to every session and 1,849 once invoked, about $0.0006 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 skills, from other repositories
agent-ready-auth-md
Sub-skill: Implement Auth.md for agent registration discovery. Serve /auth.md with OAuth metadata at /.well-known/oauth-protected-resource and authorization server endpoints.
agent-ready-dns-aid
Sub-skill: Implement DNS-AID records so agents discover endpoints through DNS. Use SVCB/HTTPS records under agents namespace with alpn and connection parameters.
agent-ready-link-headers
Sub-skill de agent-ready-cloudflare: Implement Link Response Headers.
agent-ready-markdown-negotiation
Sub-skill de agent-ready-cloudflare: Implement Markdown Content Negotiation.
agent-ready-api-catalog
Sub-skill de agent-ready-cloudflare: Implement API Catalog.
agent-ready-mcp-server-card
Sub-skill de agent-ready-cloudflare: Implement MCP Server Card.