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 1Mangesh1/hipaa-guardian --skill fhir-hl7-validatorgit clone --depth 1 https://github.com/1Mangesh1/hipaa-guardianWrote 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/1mangesh1/hipaa-guardian/fhir-hl7-validator)<a href="https://agentmods.dev/skills/1mangesh1/hipaa-guardian/fhir-hl7-validator"><img src="https://agentmods.dev/badge/skills/1mangesh1/hipaa-guardian/fhir-hl7-validator/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/1mangesh1/hipaa-guardian/fhir-hl7-validator"><img src="https://agentmods.dev/badge/skills/1mangesh1/hipaa-guardian/fhir-hl7-validator.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.00102 | $0.01752 |
| Opus 5.5 | $0.00041 | $0.00701 |
| Sonnet 5.5 | $0.00020 | $0.00350 |
| Haiku 4.5 | $0.00010 | $0.00175 |
Grade A, and why
fhir-hl7-validator 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 2mo 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FHIR & HL7 Validator
Healthcare data format validation skill for AI agents. Validates FHIR R5 resources, HL7 v2 messages, and CDA clinical documents. Ensures healthcare data interchange compliance with HL7 standards and identifies schema violations, missing required fields, and interoperability issues.
Capabilities
- FHIR Validation - Validate FHIR R5 resources against official schemas
- HL7 Message Parsing - Parse and validate HL7 v2.x messages (ADT, ORU, OBX, RXO)
- CDA Document Validation - Validate Clinical Document Architecture (CDA) R2 documents
- Schema Compliance - Check resources against FHIR specification and UK Core
- Data Type Validation - Verify FHIR data types (Identifier, CodeableConcept, Reference, etc.)
- Reference Resolution - Validate internal and external references
- Cardinality Checking - Ensure required vs. optional field compliance
- Terminology Validation - Check value sets and coding systems (SNOMED CT, LOINC, ICD-10)
- Interoperability Analysis - Identify implementation guide adherence
- Error Reporting - Generate detailed validation error reports with remediation
Usage
/fhir-hl7-validator [command] [target] [options]
Commands
validate-fhir <file>- Validate FHIR JSON/XML resourcevalidate-hl7 <file>- Validate HL7 v2 messagevalidate-cda <file>- Validate CDA clinical documentparse-fhir <file>- Parse and display FHIR resource structureparse-hl7 <file>- Parse and display HL7 segmentscheck-references <file>- Validate all resource referencescheck-terminology <file>- Validate coding systems and value setsbulk-validate <directory>- Validate multiple filesreport <output-format>- Generate validation report (JSON, markdown, HTML)
Options
--version <ver>- FHIR version (default: R5; also 4.0, 3.0)--variant <name>- Implementation guide (e.g., uk-core, us-core)--strict- Enforce must-support constraints--terminology-check- Validate coding systems (enables online lookup)--output <file>- Write report to file--format <type>- Output format: json, markdown, html, xml
What ships with it
3 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.
- 2mo ago First seen · 212 lines · 102 tokens per session scan A f177850d5911
fhir-hl7-validator is a skill published in the GitHub repository 1Mangesh1/hipaa-guardian (8 stars, last pushed 4mo ago), licensed MIT. It adds 102 tokens to every session and 1,752 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
test-native-extension
Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…
test-site
Tests a deployed, activated Power Pages site at runtime using browser-based navigation, page crawling, and API request verification via Playwright. Use when the user wants to test, verify, or smoke-test their deployed site.
create-formal-verification-skill
Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in any language, with whichever verification tool fits. Use for /create-formal-verification-skill, "model-check this race", "prove this invariant", or when concurrency, retries, state machines, parsers…
tdd
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
principle-prove-it-works
Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'.