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 hitech-breach-notificationgit 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/hitech-breach-notification)<a href="https://agentmods.dev/skills/vaquarkhan/compliance-agent-skills/hitech-breach-notification"><img src="https://agentmods.dev/badge/skills/vaquarkhan/compliance-agent-skills/hitech-breach-notification/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/hitech-breach-notification"><img src="https://agentmods.dev/badge/skills/vaquarkhan/compliance-agent-skills/hitech-breach-notification.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.00165 | $0.02268 |
| Opus 5 | $0.00082 | $0.01134 |
| Sonnet 5 | $0.00033 | $0.00454 |
| Haiku 4.5 | $0.00016 | $0.00227 |
Grade A, and why
hitech-breach-notification 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 11d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HITECH Breach Notification
Overview
The Health Information Technology for Economic and Clinical Health (HITECH) Act (2009), codified at 42 U.S.C. §17921–17923 and implemented through HIPAA Omnibus Rule amendments, strengthened breach notification, extended direct liability to business associates (BAs), and increased civil monetary penalties.
| HITECH element | Requirement | Primary reference |
|---|---|---|
| Breach notification | Individual, HHS, media (if >500 in state) | 45 CFR §164.400–414; 42 U.S.C. §17921 |
| Unsecured PHI | Breach applies to PHI not rendered unusable/unreadable/indecipherable | 45 CFR §164.402; HHS encryption guidance |
| BA liability | BAs directly liable for Security, Privacy, Breach Notification | 45 CFR §160.402(c) |
| OCR reporting | HHS breach portal; immediate if ≥500 individuals | HHS Breach Portal |
| Penalty tiers | Four tiers under HITECH (willful neglect, correction) | 42 U.S.C. §1320d-5 |
| Accounting of disclosures | Expanded accounting; breach may trigger disclosure log review | 45 CFR §164.528 |
Relationship to breach-incident-response: Use that skill for containment, scope, and cross-framework incident orchestration. This skill adds HITECH-specific legal depth: unsecured PHI analysis, OCR portal mechanics, BA direct notification obligations, media triggers, and penalty-tier documentation.
AI/agent scenarios: LLM vendor without BAA receives ePHI prompts; MCP Postgres leak of session logs; failed redaction gate (agent.py) leading to model log retention; BA LLM subprocessors.
When to Use
Use this skill when:
- HITECH breach determination after initial incident classification (
breach-incident-responseStep 4 complete) - Preparing HHS OCR breach portal submission (≥500 immediate; <500 annual aggregation)
- Analyzing whether PHI was secured (encryption per NIST SP 800-111 or equivalent) for safe harbor
- Business associate (LLM cloud, MCP host) must notify covered entity within 60 days of discovery (§164.410)
- Media notification required (>500 residents of a state or jurisdiction)
- Penalty exposure assessment and corrective action planning (willful neglect tiers)
- Accounting of disclosures update for breach-related unauthorized access
- Auditing HITECH compliance of agent pipelines post-incident
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.
- 11d ago First seen · 167 lines · 165 tokens per session scan A 1d36fa873ea7
hitech-breach-notification is a skill published in the GitHub repository vaquarkhan/compliance-agent-skills (2 stars, last pushed 18d ago), licensed MIT. It adds 165 tokens to every session and 2,268 once invoked, about $0.0008 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.