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 vaquarkhan/compliance-agent-skills --skill hipaa-technical-safeguardsgit clone --depth 1 https://github.com/vaquarkhan/compliance-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/vaquarkhan/compliance-agent-skills/hipaa-technical-safeguards)<a href="https://agentmods.dev/skills/vaquarkhan/compliance-agent-skills/hipaa-technical-safeguards"><img src="https://agentmods.dev/badge/skills/vaquarkhan/compliance-agent-skills/hipaa-technical-safeguards/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/vaquarkhan/compliance-agent-skills/hipaa-technical-safeguards"><img src="https://agentmods.dev/badge/skills/vaquarkhan/compliance-agent-skills/hipaa-technical-safeguards.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.00119 | $0.02043 |
| Opus 5 | $0.00060 | $0.01022 |
| Sonnet 5 | $0.00024 | $0.00409 |
| Haiku 4.5 | $0.00012 | $0.00204 |
Grade A, and why
hipaa-technical-safeguards 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 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.
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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HIPAA Technical Safeguards
Overview
This skill implements the HIPAA Security Rule Technical Safeguards at 45 CFR §164.312:
| Standard | Regulation | Agent/MCP focus |
|---|---|---|
| Access control | §164.312(a)(1) | Unique user IDs, emergency access, automatic logoff, encryption/decryption |
| Audit controls | §164.312(b) | Tamper-evident logs of ePHI access via agents and MCP tools |
| Integrity | §164.312(c)(1) | Mechanisms to authenticate ePHI is not improperly altered or destroyed |
| Person or entity authentication | §164.312(d) | Verify identity of persons/systems accessing ePHI |
| Transmission security | §164.312(e)(1) | Integrity controls and encryption for ePHI in transit to LLMs and MCP |
AI agents introduce novel attack surfaces: tool calls may exfiltrate ePHI, MCP servers may log prompts, and LLM providers may process data outside BAA coverage. This skill produces a control-by-control assessment with evidence, not generic "HIPAA checklist" advice.
When to Use
Use this skill when:
- Designing or auditing an AI agent that may touch ePHI
- Evaluating MCP server access to databases, files, or APIs containing PHI
- Reviewing encryption (TLS 1.2+, at-rest) for agent-to-LLM and agent-to-MCP paths
- Mapping §164.312 implementation specifications (required vs addressable) to your stack
- Assessing audit logging for agent sessions and tool invocations
- Validating authentication (OAuth 2.1, MFA, service accounts) for ePHI systems
Do not use this skill when:
- Legal review of Business Associate Agreements (use
hipaa-baa-vendor-assessment) - Configuring Presidio redaction pipelines (use
hipaa-phi-redaction-pipeline) - PCI payment card data controls (use PCI skills)
- SOC 2 TSC mapping without HIPAA overlay (use
soc2-trust-services-criteria)
Core Process
Execute steps in order. Reference 45 CFR §164.312 explicitly in findings.
Step 1: ePHI data flow inventory
- Diagram all paths where ePHI may enter, transit, or exit the agent system:
- User prompts, uploaded documents, MCP query results, LLM responses
- Logging, monitoring, error reporting, third-party analytics
- Classify each hop: creates, reads, updates, transmits, or stores ePHI.
- Identify Business Associates at each hop (LLM vendor, cloud host, MCP operator).
- Save artifact:
ephi-data-flow-{id}.json.
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 · 149 lines · 119 tokens per session scan A 834f7fdaa2cd
hipaa-technical-safeguards is a skill published in the GitHub repository vaquarkhan/compliance-agent-skills (2 stars, last pushed 19d ago), licensed MIT. It adds 119 tokens to every session and 2,043 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.
Other skills, from other repositories
cmmc-assessment-objectives
Verbatim reference for all 320 NIST 800-171A Rev 2 assessment objectives, plus the Rev 2 → Rev 3 control crosswalk. Use for AO-level lookups (e.g., 3.1.1[c]), evidence planning, and forward-mapping to Rev 3. Pairs with cmmc-expert.
dora-expert
DORA expert for EU financial entities. Deep knowledge of Digital Operational Resilience Act including 5 pillars, ICT risk management, incident reporting, resilience testing, third-party oversight, and information sharing for financial sector digital resilience.
cmmc-expert
CMMC v2.0 expert for DoD contractors. Covers NIST 800-171 Rev 2 (14 families, 110 controls), SPRS scoring, POA&M rules, 32 CFR Part 170, DFARS clauses, scoping, ESP/CSP, C3PAO assessment lifecycle, and Rev 2 → Rev 3 transition.
eu-nis2-expert
EU NIS2 Directive (Directive (EU) 2022/2555) expert. Reference-depth knowledge of essential vs important entity classification, Article 20 governance, the Article 21 ten cybersecurity risk-management measures, the Article 23 24h/72h/1mo incident-reporting timeline, and supervision/enforcement under Articles 32-34.…
gdpr-expert
GDPR expert for EU privacy compliance. Deep knowledge of General Data Protection Regulation including 99 articles, 7 principles, 6 lawful bases, data subject rights, DPO requirements, DPIA, breach notification, cross-border transfers, and enforcement.
glba-expert
GLBA expert for financial institutions. Deep knowledge of Gramm-Leach-Bliley Act including Safeguards Rule (16 CFR Part 314), Privacy Rule (16 CFR Part 313), FTC enforcement, information security program requirements, vendor management, and consumer privacy notices.