demographic-modeling

demographic-modeling is a skill for Claude Code from Cadasto/openehr-assistant-plugin. It costs 126 tokens per session (1,849 once invoked), scanned A, original, MIT.

A design guide for demographic information in openEHR, including people, organizations, groups, agents, roles, abilities, and relationships. openEHR is a standard for electronic health records, and demographic information describes the parties involved in care.

In plain words
What is it for?
Use it to plan models for people or organizations, define their roles and capabilities, and represent relationships between parties.
Why use it?
It helps keep identity, roles, and relationships organized according to openEHR’s model. This reduces confusion when representing who people and organizations are and how they relate to one another.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the openehr-assistant plugin — 8 skills, 3 commands, 3 agents, 2 hooks, 1 MCP server shipped together

Good fit Use it to plan models for people or organizations, define their roles and capabilities, and represent relationships between parties.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cadasto/openehr-assistant-plugin/demographic-modeling
Install

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.

Any agent
npx skills add Cadasto/openehr-assistant-plugin --skill demographic-modeling
Clone the repo
git clone --depth 1 https://github.com/Cadasto/openehr-assistant-plugin

Made for: Claude Code.

Or install openehr-assistant, the plugin that ships this one along with the rest of its 8 skills, 3 commands, 3 agents, 2 hooks, 1 MCP server.

Wrote 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.

agentmods badge for demographic-modeling

README.md
[![agentmods](https://agentmods.dev/badge/skills/cadasto/openehr-assistant-plugin/demographic-modeling/github.svg)](https://agentmods.dev/skills/cadasto/openehr-assistant-plugin/demographic-modeling)
Your own site
<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.

agentmods 80×15 button for demographic-modeling

Your own site · 80×15
<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>
Per session 126 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,849 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 10d ago against content hash 06c65eaee286, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

skills/demographic-modeling/SKILL.md · 183 lines

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-demographic guide loaded in Step 1 is authoritative — if they disagree, follow the guide (or confirm against type_specification_get).

Conflict Resolution

When guides conflict, apply this priority (highest first):

  1. Rules and structural constraints
  2. Privacy and separation principles
  3. Anti-patterns
  4. Principles and examples
  5. 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.

Read the full file on GitHub · 183 lines

Changes

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.

  1. 10d ago First seen · 183 lines · 126 tokens per session scan A 06c65eaee286

Subscribe to this mod's changes

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.