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 hamzabellouch/agent-skills --skill fhir-hl7-health-datagit clone --depth 1 https://github.com/hamzabellouch/agent-skillsWrote 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/hamzabellouch/agent-skills/fhir-hl7-health-data)<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/fhir-hl7-health-data"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/fhir-hl7-health-data/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/hamzabellouch/agent-skills/fhir-hl7-health-data"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/fhir-hl7-health-data.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.00047 | $0.01835 |
| Opus 5.5 | $0.00019 | $0.00734 |
| Sonnet 5.5 | $0.00009 | $0.00367 |
| Haiku 4.5 | $0.00005 | $0.00184 |
Grade A, and why
fhir-hl7-health-data 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 1mo 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FHIR R4/R5 & HL7 v2 Health Data Integration
Overview
This skill provides standards for digital health interoperability using HL7 FHIR (Fast Healthcare Interoperability Resources) R4/R5 and legacy HL7 v2.x messaging. It covers FHIR JSON resources (Patient, Observation, Encounter, Condition), SMART on FHIR OAuth2 scoping, HL7 v2 MLLP framing/parsing, and HIPAA-compliant data security.
1. Healthcare Data Interoperability Principles
- FHIR Spec Compliance: Stick strictly to standard FHIR R4/R5 resource schemas. Use extensions (
Extension) only when necessary and register custom profiles viaStructureDefinition. - SMART on FHIR Security: Enforce fine-grained OAuth2 scopes (
patient/Patient.read,user/Observation.write,launch/patient). Enforce OpenID Connect for practitioner identity verification. - HL7 v2 to FHIR Mapping: Convert incoming legacy HL7 v2 pipeline messages (ADT, ORU, MDM) into standard FHIR bundles (
Bundleof typetransactionorbatch) for modern storage. - Idempotent Resource Mutations: Use conditional updates (
PUT /Patient?identifier=system|value) to prevent duplicating patient records across EHR sync pipelines. - HIPAA & PHI Security: Encrypt all Protected Health Information (PHI) in transit (TLS 1.3) and at rest (AES-256). Audit access via FHIR
AuditEventresources.
2. Health Data Pipeline Architecture
[ Legacy EHR System ] ──(HL7 v2 ADT/ORU over MLLP)
│
▼
[ Interoperability Engine ] ──(HL7 v2 Parser & FHIR Converter)
│
│ FHIR Transaction Bundle (HTTPS / SMART on FHIR)
▼
[ HAPI FHIR / Medplum Server ] ◀──(OAuth2 Bearer Token)── [ Patient Portal / Mobile App ]
| FHIR Resource | Primary Medical Data | Key Search Parameters |
|---|---|---|
Patient |
Demographics, Identifiers, Contact Info | _id, identifier, name, birthdate |
Observation |
Lab Results, Vital Signs, Social History | patient, category, code (LOINC), date |
Condition |
Diagnoses, Problems, Medical History | patient, clinical-status, code (SNOMED CT) |
Encounter |
Inpatient/Outpatient visits, Stays | patient, status, class, date |
Bundle |
Container for multiple resources | type=transaction, type=searchset |
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.
- 1mo ago First seen · 200 lines · 47 tokens per session scan A 238812d4868a
fhir-hl7-health-data is a skill published in the GitHub repository hamzabellouch/agent-skills (8 stars, last pushed 11d ago), licensed MIT. It adds 47 tokens to every session and 1,835 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
ubiquitous-language
Maintain a project thesaurus (domain glossary) following DDD ubiquitous language principles. Use PROACTIVELY when naming anything: variables, functions, classes, modules, database fields, API endpoints, events, files, or directories. Also use when the user asks to "create thesaurus", "update glossary", "add term"…
laravel-expert
Laravel & PHP Development Instructions for GitHub Copilot.
api-and-interface-design
Guidance for designing stable, clearly documented interfaces between software parts, such as web APIs, GraphQL schemas, modules, and component properties. It covers defining the contract first, limiting accidental dependencies, and planning safe changes.
nodejs-codestyle
Custom Instructions: Node.js Backend & Architecture Expert.
php-laravel-codestyle
Custom Instructions: PHP 8+ & Laravel Architecture Expert.
api-design
Procedure to add or change an HTTP (OpenAPI) or gRPC (protobuf) API contract: edit the spec first, check breaking changes with oasdiff or buf, version and deprecate, and add contract tests. Use when you add or change an endpoint, request or response schema, or a proto service.