Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/aks129/HealthClawGuardrailsnpx agentmods add skills/aks129/healthclawguardrails/healthex-exportWrote 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/aks129/healthclawguardrails/healthex-export)<a href="https://agentmods.dev/skills/aks129/healthclawguardrails/healthex-export"><img src="https://agentmods.dev/badge/skills/aks129/healthclawguardrails/healthex-export/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/aks129/healthclawguardrails/healthex-export"><img src="https://agentmods.dev/badge/skills/aks129/healthclawguardrails/healthex-export.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Supply Chain · line 119 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
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.00127 | $0.01815 |
| Opus 5 | $0.00063 | $0.00907 |
| Sonnet 5 | $0.00025 | $0.00363 |
| Haiku 4.5 | $0.00013 | $0.00181 |
Grade A, and why
healthex-export scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "http://localhost:5000/r6/fhir/Observation?_count=200" \ How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HealthClaw HealthEx Export
scripts/export_healthex.py automates the full pipeline from local HealthClaw
FHIR store → de-identified, Curatr-pre-tagged FHIR R4 transaction Bundle.
Replaces the manual Claude session pull for personal health data export.
Quick Start
# Basic export — all clinical resource types for a tenant
python scripts/export_healthex.py --tenant-id my-tenant
# Export + immediately import into a second tenant
python scripts/export_healthex.py \
--tenant-id my-tenant \
--import \
--import-tenant my-archive-tenant \
--step-up-secret $STEP_UP_SECRET
# Preview what would be exported (no file written)
python scripts/export_healthex.py --tenant-id my-tenant --dry-run
# Export specific resource types
python scripts/export_healthex.py \
--tenant-id my-tenant \
--types Condition Observation AllergyIntolerance Immunization MedicationRequest
Output
Bundle written to exports/healthex-<YYYY-MM-DD>.json by default.
Override with --output /path/to/file.json.
Format: FHIR R4 transaction Bundle ("type": "transaction") with PUT entries,
ready for POST /Bundle/$ingest-context or direct use with import_healthex.py.
Resource Types Exported (default)
| Type | Notes |
|---|---|
| Patient | De-identified: name/address/telecom removed, EHR identifiers stripped |
| Condition | Full — diagnoses, clinical/verification status, onset/abatement |
| Observation | Full — labs, vitals, social history (smoking, BMI, etc.) |
| AllergyIntolerance | Full |
| Immunization | Full |
| MedicationRequest | Full |
| Procedure | Full |
| DiagnosticReport | Full |
| CarePlan | Full |
| Coverage | Full |
| Encounter | Full |
Pass --types <ResourceType> ... to limit to a subset.
De-identification
Applied automatically (skip with --no-deidentify).
Removed from Patient:
name— full nameaddress— street, city, state, ziptelecom— phone, emailphoto— base64 imagescontact— emergency contacts- OID-namespaced identifiers (EHR-internal MRNs, Epic IDs, CEID, EID, EMPI, etc.)
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.
- 12d ago First seen · 181 lines · 127 tokens per session scan A f70f842e6ee1
healthex-export is a skill published in the GitHub repository aks129/HealthClawGuardrails (30 stars, last pushed today), licensed MIT. It adds 127 tokens to every session and 1,815 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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-fhir
Design RESTful clinical data exchanges using HL7 FHIR standards.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
microservices-patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
python-sdk
Implement or modify Python SDK behavior under python/composio, including tools, toolkits, sessions, auth configs, connected accounts, client integration, and shared Python models. Use for Python core runtime/API work; pair with python-testing and cross-sdk-parity when TypeScript must match.