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 realactivity/tula --skill health-recordsgit clone --depth 1 https://github.com/realactivity/tulaWrote 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/realactivity/tula/health-records)<a href="https://agentmods.dev/skills/realactivity/tula/health-records"><img src="https://agentmods.dev/badge/skills/realactivity/tula/health-records/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/realactivity/tula/health-records"><img src="https://agentmods.dev/badge/skills/realactivity/tula/health-records.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.00113 | $0.01410 |
| Opus 5 | $0.00056 | $0.00705 |
| Sonnet 5 | $0.00023 | $0.00282 |
| Haiku 4.5 | $0.00011 | $0.00141 |
Grade A, and why
health-records 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
health-records
When to Use
✅ Use when:
- The user asks to connect, link, refresh, or pull records from a patient portal
- Trending a lab, vital, or medication across multiple visits
- "What does my chart say about X" (problems, meds, allergies, immunizations)
- Searching clinical notes for a topic, symptom, or referral
When NOT to Use
❌ Don't use when:
- The user sends a PDF or screenshot -> use
med-pdf - The user wants to draft a clinician message -> use
epic-note - Records already pulled this session - read the existing JSON
- Anything that would send PHI to an external service
Setup
Profile. Resolve from the precedence in
references/profile-schema.md
(skill config -> env var -> ~/.openclaw/workspace/memory/profile.yaml).
Use identity.short_name when addressing the user in status messages.
The skill never contains the profile.
Workflow
-
Check backend first -
node {baseDir}/scripts/check-backend.mjs- Confirms
/healthand/api/vendorsare reachable. - If self-hosted, set
HEALTH_SKILLZ_BASE_URLbefore this step.
- Confirms
-
Create session -
node {baseDir}/scripts/create-session.mjs- Outputs JSON:
sessionId,userUrl,privateKeyJwk. - Save
privateKeyJwkfor step 3. Never echo it back.
- Outputs JSON:
-
Show the link. Present
userUrlto the user as a single markdown link labeled "Connect your health records". Don't narrate the crypto. Wait for the user to finish the OAuth flow; they may connect multiple providers. -
Finalize & decrypt -
node {baseDir}/scripts/finalize-session.mjs <sessionId> '<privateKeyJwk>' <outDir>outDirinside~/.openclaw/workspace/. Suggested:~/.openclaw/workspace/.health-records-cache/<YYYY-MM-DD>/.- NDJSON progress on stdout; final line is
{"status":"done",...}. - One JSON file per provider, slugified by name.
-
Reason. Open with one clinical sentence (scope, span, what stands out), then 2-3 specific directions tied to what's actually there - not a generic dashboard. See
references/fhir-guide.mdfor resource shapes, LOINC codes, and the analysis philosophy.
What ships with it
9 files 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.
- 10d ago First seen · 127 lines · 113 tokens per session scan A cf85cf143e1e
health-records is a skill published in the GitHub repository realactivity/tula (45 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 113 tokens to every session and 1,410 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-30.
Other skills, from other repositories
healthcare-expert
Expert-level healthcare systems, medical informatics, HIPAA compliance, and health data standards. Use when the user mentions medical, HIPAA, HL7, FHIR, or EHR, or when the task involves Healthcare IT, Standards and Protocols, Regulatory Compliance, or Security and Compliance.
ehr-data-parsing
Parse and extract clinical data from HL7v2 messages and FHIR R4 resources using Python. Use when the user mentions HL7v2, HL7, FHIR, PID segment, OBX segment, MSH segment, Patient resource, Observation resource, Condition resource, MedicationRequest, EHR data extraction, clinical message parsing, FHIR bundle, HL7 to…
telemetry-inspect
Inspects the OrchestKit telemetry pipeline for the current project — lists all known telemetry files with write counts, sizes, schema status, growth trend, and orphan detection. Use when verifying the observability pipeline is healthy, debugging a missing writer, or auditing which files have schema locks vs. which are…
biomcp-research
Do biomedical literature and variant research with the BioMCP CLI, and file what you learn about the tool itself as issues in the biomcp repo.
system_status
Check system health -- disk usage, memory, running processes, uptime.
branch_health
Quick health check -- test counts and file stats for AIPass branches.