HIPAA Safe Harbor Coverage Audit
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
Executes breach notification under HIPAA Breach Notification Rule (45 CFR 164.400-414).
Install Hipaa Breach Notification
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill hipaa-breach-notification -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills hipaa-breach-notification --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/privacy/hipaa-breach-notification .claude/skills/hipaa-breach-notification && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "hipaa-breach-notification" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-breach-notification into .claude/skills/hipaa-breach-notification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hipaa-breach-notification", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-breach-notificationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill hipaa-breach-notification -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills hipaa-breach-notification --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/privacy/hipaa-breach-notification .agents/skills/hipaa-breach-notification && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hipaa-breach-notification" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-breach-notification into .agents/skills/hipaa-breach-notification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hipaa-breach-notification", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill hipaa-breach-notification -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills hipaa-breach-notification --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/privacy/hipaa-breach-notification .cursor/skills/hipaa-breach-notification && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "hipaa-breach-notification" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-breach-notification into .cursor/skills/hipaa-breach-notification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hipaa-breach-notification", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mukul975/Privacy-Data-Protection-Skills.git --path skills/privacy/hipaa-breach-notification--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill hipaa-breach-notification -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills hipaa-breach-notification --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/privacy/hipaa-breach-notification .gemini/skills/hipaa-breach-notification && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "hipaa-breach-notification" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-breach-notification into .gemini/skills/hipaa-breach-notification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hipaa-breach-notification", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mukul975/Privacy-Data-Protection-Skills hipaa-breach-notificationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill hipaa-breach-notification -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/privacy/hipaa-breach-notification .github/skills/hipaa-breach-notification && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "hipaa-breach-notification" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-breach-notification into .github/skills/hipaa-breach-notification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hipaa-breach-notification", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill hipaa-breach-notification -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills hipaa-breach-notification --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/privacy/hipaa-breach-notification .opencode/skills/hipaa-breach-notification && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "hipaa-breach-notification" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-breach-notification into .opencode/skills/hipaa-breach-notification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hipaa-breach-notification", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
hipaa-breach-notification- GitHub stars
- 301
- Token cost
- ~2.3k tokens
- SKILL.md length
- 1,141 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Executes breach notification under HIPAA Breach Notification Rule (45 CFR 164.400-414).
- Works in 3 steps: Business associate must notify the… → The notification must include:… → The covered entity is ultimately…
- Tasks that involve Healthcare and finance regulation
- SKILL.md covers Overview, Key Definitions, Four-Factor Breach Risk… and Notification Requirements, plus 4 more sections
- Runs Python scripts from its folder
What it does
Hipaa Breach Notification is an agent skill from mukul975/Privacy-Data-Protection-Skills. Executes breach notification under HIPAA Breach Notification Rule (45 CFR 164.400-414). Covers 60-day individual notification, HHS/OCR reporting for breaches of 500+ individuals (immediate) and under 500 (annual log), state attorney general notification, media notification for 500+ in a single state, and breach risk assessment using the four-factor test. Keywords: HIPAA, breach notification, PHI, HHS, OCR, covered entity, business associate.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/standards.md` and `references/workflows.md`).
It sits in Legal & Compliance, covering Healthcare and finance regulation. The repository describes itself as: 282+ structured privacy & data protection skills for AI agents. GDPR, CCPA, EU AI Act, HIPAA, LGPD, PIPL, DPDP Act. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Healthcare and finance regulation
Example prompts
- “Use the hipaa-breach-notification skill to execute breach notification under HIPAA Breach Notification Rule (45 CFR 164.400-414)”
- “/hipaa-breach-notification”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Business associate must notify the covered entity of a breach without unreasonable delay, and no later than 60 days from discovery (or a…
- The notification must include: identification of each individual affected (if known), and any other available information the covered…
- The covered entity is ultimately responsible for providing all required notifications.
What it can do on your machine
Read from SKILL.md and the folder at commit 9b2ef9e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Hipaa Breach Notification loads about 2.3k tokens when it runs, and up to ~4.6k if it reads all its reference files. Until then it costs about 118 tokens; SKILL.md has 1,141 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 1,141 words, ~2,293 tokens.
Download SKILL.mdSave it as
.claude/skills/hipaa-breach-notification/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- hipaa-breach-notification
- description
- Executes breach notification under HIPAA Breach Notification Rule (45 CFR 164.400-414). Covers 60-day individual notification, HHS/OCR reporting for breaches of 500+ individuals (immediate) and under 500 (annual log), state attorney general notification, media notification for 500+ in a single state, and breach risk assessment using the four-factor test. Keywords: HIPAA, breach notification, PHI, HHS, OCR, covered entity, business associate.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- data-breach-response
- metadata.tags
- hipaa, breach-notification, phi, hhs-ocr, covered-entity, business-associate
Executing HIPAA Breach Notification
Overview
The HIPAA Breach Notification Rule (45 CFR §§164.400-414) requires HIPAA covered entities and their business associates to provide notification following a breach of unsecured protected health information (PHI). This skill covers the complete HIPAA breach notification workflow, including the four-factor risk assessment, individual notification requirements, HHS/OCR reporting obligations, state attorney general notification, and media notification thresholds.
Key Definitions
| Term | Definition | Source |
|---|---|---|
| Breach | Acquisition, access, use, or disclosure of PHI in a manner not permitted under the Privacy Rule that compromises the security or privacy of the PHI | 45 CFR §164.402 |
| Unsecured PHI | PHI that is not rendered unusable, unreadable, or indecipherable to unauthorized persons through encryption or destruction per HHS guidance | 45 CFR §164.402 |
| Covered Entity | Health plan, healthcare clearinghouse, or healthcare provider that transmits health information electronically | 45 CFR §160.103 |
| Business Associate | Person or entity that creates, receives, maintains, or transmits PHI on behalf of a covered entity | 45 CFR §160.103 |
| Discovery | The first day the breach is known to the covered entity (or would have been known through reasonable diligence) | 45 CFR §164.404(a)(2) |
Four-Factor Breach Risk Assessment — 45 CFR §164.402(2)
A covered entity must assess the probability that PHI has been compromised using four factors:
Factor 1: Nature and Extent of PHI Involved
- What types of identifiers were involved? (name, SSN, date of birth, diagnosis codes, treatment records)
- How many records were involved?
- Does the PHI include information that increases the risk of identity theft or financial fraud (SSN, financial information)?
- Does the PHI include clinical information that could cause stigma or embarrassment (mental health, substance abuse, HIV status, reproductive health)?
Factor 2: Unauthorized Person Who Used or Received the PHI
- Was the recipient another covered entity or business associate bound by HIPAA?
- Was the recipient a person with no obligation to protect the PHI?
- Is the recipient known or unknown?
- Does the recipient have the ability to re-identify de-identified data?
Factor 3: Whether the PHI Was Actually Acquired or Viewed
- Is there evidence the PHI was actually accessed or viewed?
- Was the PHI returned unopened (e.g., misdirected mail returned by postal service)?
- Do forensic logs show the data was downloaded, copied, or transmitted?
- Was the exposure theoretical (e.g., server was accessible but no evidence of access)?
Factor 4: Extent to Which Risk Has Been Mitigated
- Was the PHI recovered or destroyed?
- Did the unauthorized recipient provide assurances (written attestation) of destruction?
- Were technical controls in place that limited access (password-protected files, short exposure window)?
- Has the covered entity obtained confirmation that the PHI was not further disclosed?
Assessment Outcome
If the four-factor assessment demonstrates a low probability that the PHI has been compromised, the incident is not a reportable breach. The assessment must be documented. If there is any doubt, the incident should be treated as a reportable breach.
Notification Requirements
Individual Notification — 45 CFR §164.404
| Requirement | Detail |
|---|---|
| Timeline | Without unreasonable delay, no later than 60 calendar days from discovery |
| Method | First-class mail to last known address; email if individual has agreed to electronic notice |
| Content — Brief description of breach | What happened and date(s) of breach and discovery |
| Content — Types of information | Description of PHI types involved (not the actual PHI) |
| Content — Protective steps | Steps individual should take to protect from potential harm |
| Content — Entity's actions | Brief description of what the entity is doing to investigate, mitigate harm, and prevent recurrence |
| Content — Contact information | Toll-free number, email, website, or postal address for questions |
| Substitute notice (10+ individuals with insufficient contact info) | Conspicuous posting on entity's website for 90 days OR conspicuous notice in major print or broadcast media serving the area. Must include toll-free number active for 90 days. |
| Urgent notice | If there is possible imminent misuse, notice by telephone or other means in addition to written notice |
HHS/OCR Notification — 45 CFR §164.408
| Breach Size | Reporting Method | Timeline |
|---|---|---|
| 500 or more individuals | HHS Breach Portal (ocrportal.hhs.gov) | Without unreasonable delay, no later than 60 days from discovery. HHS posts on the "Wall of Shame" (breach portal) |
| Fewer than 500 individuals | HHS Breach Portal — annual log | Within 60 days of the end of the calendar year in which the breach was discovered (by March 1 of the following year) |
Show full SKILL.md (446 more words)Show less
State Attorney General Notification — 45 CFR §164.412
| Requirement | Detail |
|---|---|
| Threshold | Breaches involving residents of the state; most states require notification for 500+ affected residents |
| Timeline | Concurrent with or prior to individual notification |
| Content | Same as individual notification content |
| Method | Written notice to the attorney general of each state where affected individuals reside |
Media Notification — 45 CFR §164.406
| Requirement | Detail |
|---|---|
| Threshold | Breach affecting 500 or more individuals in a single state or jurisdiction |
| Timeline | Without unreasonable delay, no later than 60 days from discovery |
| Method | Prominent media outlets serving the state or jurisdiction (newspaper, TV, radio) |
| Content | Same as individual notification content |
Breach Exceptions — 45 CFR §164.402(1)
Three exceptions to the definition of "breach" (not reportable even if unsecured PHI is involved):
Exception 1: Unintentional Acquisition
Good-faith, unintentional acquisition, access, or use of PHI by a workforce member or person acting under the covered entity's authority, if made within the scope of authority and without further impermissible use or disclosure.
Exception 2: Inadvertent Disclosure Within Organization
Inadvertent disclosure of PHI by a person authorized to access PHI at a covered entity or business associate to another person authorized to access PHI at the same entity, and the PHI is not further used or disclosed impermissibly.
Exception 3: Good Faith Belief of No Retention
Disclosure of PHI where the covered entity or business associate has a good-faith belief that the unauthorized person would not reasonably have been able to retain the information.
Business Associate Obligations — 45 CFR §164.410
- Business associate must notify the covered entity of a breach without unreasonable delay, and no later than 60 days from discovery (or a shorter period specified in the BAA).
- The notification must include: identification of each individual affected (if known), and any other available information the covered entity needs to provide individual notification.
- The covered entity is ultimately responsible for providing all required notifications.
Penalties for Non-Compliance
| Tier | Knowledge Level | Per Violation | Annual Cap |
|---|---|---|---|
| Tier 1 | Did not know and could not have known | $137 - $68,928 | $2,067,813 |
| Tier 2 | Reasonable cause, not willful neglect | $1,379 - $68,928 | $2,067,813 |
| Tier 3 | Willful neglect, corrected within 30 days | $13,785 - $68,928 | $2,067,813 |
| Tier 4 | Willful neglect, not corrected | $68,928 - $2,067,813 | $2,067,813 |
(Penalty amounts adjusted for inflation per Federal Register notice, effective 2025.)
Integration with State Laws
HIPAA breach notification does not preempt state breach notification laws that provide greater protection or additional requirements. Covered entities must comply with both HIPAA and applicable state laws. In practice:
- HIPAA 60-day deadline is the outer limit; some states impose shorter deadlines.
- State content requirements may exceed HIPAA minimums.
- State AG notification may be required even for breaches under 500 individuals depending on state law.
© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (scripts, references, assets) in skills/privacy/hipaa-breach-notification of mukul975/Privacy-Data-Protection-Skills.
- SKILL.md
- assets/template.md
- references/standards.md
- references/workflows.md
- scripts/process.py
Open the folder on GitHubat commit 9b2ef9e
Compare with similar skills
Hipaa Breach Notification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Hipaa Breach Notification this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| HIPAA Pre-Deployment Compliance Checkmaziyarpanahi/openmed | 5.5k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| ISO Standards Readiness EvidenceK-Dense-AI/scientific-agent-skills | 48k | 1 repos | ~4.6k | Automated safety check: Notes | MIT | |
| Fda Consultant Specialistdavila7/claude-code-templates | 33k | 1 repos | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
HIPAA Pre-Deployment Compliance Check
maziyarpanahi/openmed
Walks a data pipeline against the HIPAA Privacy and Security Rule checklist and produces a gap report before it processes patient data.
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
ISO Standards Readiness Evidence
K-Dense-AI/scientific-agent-skills
Organizes scope, controlled documents, risk files and traceability into draft evidence for human review against ISO 13485, 14971, 17025 and 15189.
Fda Consultant Specialist
davila7/claude-code-templates
Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.
Grc Knowledge
mlunato47/claude-grc-plugin
Senior GRC analyst expertise across 18 compliance frameworks — NIST 800-53, FedRAMP (Rev5 + 20x/CR26, KSIs, VDR/VER, Certification Classes A–D), DoD/DoW Impact Levels (IL2–IL6, DISA Cloud SRG), ITAR…
More from mukul975/Privacy-Data-Protection-Skills
All 280 skills in this repoAge Gating Services
mukul975/Privacy-Data-Protection-Skills
Implements age-gating mechanisms for online services to restrict access based on user age.
AI Data Retention
mukul975/Privacy-Data-Protection-Skills
Manages AI model retention and machine unlearning requirements.
AI Dpia
mukul975/Privacy-Data-Protection-Skills
Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing.
Dpia Mitigation Plan
mukul975/Privacy-Data-Protection-Skills
Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).
Gdpr Accountability
mukul975/Privacy-Data-Protection-Skills
Guides implementation of the GDPR accountability principle under Articles 5(2) and 24, including documentation requirements for policies, DPIAs, RoPA, training records, and breach logs.
Pia Threshold Screening
mukul975/Privacy-Data-Protection-Skills
Conducts pre-DPIA threshold screening to determine whether a full Data Protection Impact Assessment is required under GDPR Article 35.
Related
Categories
Questions about Hipaa Breach Notification
What does Hipaa Breach Notification do?
Executes breach notification under HIPAA Breach Notification Rule (45 CFR 164.400-414). Hipaa Breach Notification is an agent skill from mukul975/Privacy-Data-Protection-Skills.400-414).
When should I use Hipaa Breach Notification?
Hipaa Breach Notification fits situations like: tasks that involve Healthcare and finance regulation.
How do I install Hipaa Breach Notification in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill hipaa-breach-notification -a claude-code`. Or copy the skill folder (skills/privacy/hipaa-breach-notification in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/hipaa-breach-notification in your project. Claude Code loads it when a task matches its description.
How do I install Hipaa Breach Notification in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill hipaa-breach-notification -a codex`. Or copy the skill folder (skills/privacy/hipaa-breach-notification in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/hipaa-breach-notification in your project. Codex loads it when a task matches its description.
Can I use Hipaa Breach Notification in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill hipaa-breach-notification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hipaa-breach-notification, .gemini/skills/hipaa-breach-notification, .github/skills/hipaa-breach-notification and .opencode/skills/hipaa-breach-notification in your project.
What does Hipaa Breach Notification need to run?
Going by SKILL.md and its folder, Hipaa Breach Notification needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Hipaa Breach Notification access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Hipaa Breach Notification safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Hipaa Breach Notification use?
Hipaa Breach Notification is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Hipaa Breach Notification use?
About 2.3k tokens (SKILL.md is roughly 9.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.3k tokens, read only when the agent opens those files.
What are the alternatives to Hipaa Breach Notification?
Skills that share tags, products or a category with Hipaa Breach Notification: HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), HIPAA Pre-Deployment Compliance Check (maziyarpanahi/openmed, 5.5k stars), Hipaa Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars) and ISO Standards Readiness Evidence (K-Dense-AI/scientific-agent-skills, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hipaa Breach Notification?
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 301 GitHub stars. The repository holds 280 skills in this directory. The repository was last updated on March 16, 2026.
Source: mukul975/Privacy-Data-Protection-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.