Agent skill

Hipaa Breach Notify

by mukul975 in mukul975/Privacy-Data-Protection-Skills

Implements HIPAA breach notification requirements under 45 CFR §164.400-414.

Apache-2.0Auto-check passedLegal & Compliance

Install Hipaa Breach Notify

skills CLI
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill hipaa-breach-notify -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Privacy-Data-Protection-Skills hipaa-breach-notify --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-notify .claude/skills/hipaa-breach-notify && rm -rf skills-src

Use ~/.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/

Facts

Skill name
hipaa-breach-notify
GitHub stars
301
Token cost
~3.4k tokens
SKILL.md length
1,735 words
Files
5 (incl. scripts, references, assets)
Skills in repo
280
Repo updated
First seen
Licence
Apache-2.0

At a glance

Implements HIPAA breach notification requirements under 45 CFR §164.400-414.

  • Works in 3 steps: Unintentional good-faith acquisition:… → Inadvertent disclosure between… → Good-faith belief of non-retention: The…
  • Tasks that involve Healthcare and finance regulation
  • SKILL.md covers Overview, Definition of Breach — §164.402, Unsecured PHI — §164.402 and Notification Requirements, plus 5 more sections
  • Runs Python scripts from its folder

What it does

Hipaa Breach Notify is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implements HIPAA breach notification requirements under 45 CFR §164.400-414. Covers individual notification within 60 days, HHS reporting thresholds (500+ immediate, under 500 annual), state attorney general notification, media notification for 500+ in a state, and breach risk assessment. Keywords: HIPAA breach notification, HHS reporting, OCR breach portal, individual notice, state attorney general.

Its SKILL.md is about 3.4k 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-notify skill to implement HIPAA breach notification requirements under 45 CFR §164.400-414”
  • “/hipaa-breach-notify”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Unintentional good-faith acquisition: PHI acquired unintentionally by a workforce member or person acting under the authority of the…
  2. Inadvertent disclosure between authorized persons: PHI inadvertently disclosed by a person authorized to access PHI to another person…
  3. Good-faith belief of non-retention: The covered entity or BA has a good-faith belief that the unauthorized person to whom the disclosure…

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 Notify loads about 3.4k tokens when it runs, and up to ~5.8k if it reads all its reference files. Until then it costs about 106 tokens; SKILL.md has 1,735 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~106
When it runs · the whole SKILL.md, loaded when a task matches
~3.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.8k

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,735 words, ~3,362 tokens.

Download SKILL.mdSave it as .claude/skills/hipaa-breach-notify/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
hipaa-breach-notify
description
Implements HIPAA breach notification requirements under 45 CFR §164.400-414. Covers individual notification within 60 days, HHS reporting thresholds (500+ immediate, under 500 annual), state attorney general notification, media notification for 500+ in a state, and breach risk assessment. Keywords: HIPAA breach notification, HHS reporting, OCR breach portal, individual notice, state attorney general.
license
Apache-2.0
metadata.author
mukul975
metadata.version
1.0
metadata.domain
privacy
metadata.subdomain
healthcare-privacy
metadata.tags
hipaa, breach-notification, hhs-reporting, ocr-breach-portal, individual-notice, state-ag

HIPAA Breach Notification Rule — 45 CFR §164.400-414

Overview

The HIPAA Breach Notification Rule, added by the HITECH Act of 2009 and finalized in the Omnibus Rule of 2013 (78 FR 5566), requires covered entities and business associates to provide notification following a breach of unsecured protected health information (PHI). The rule establishes specific timeframes, content requirements, and reporting obligations that vary based on the number of individuals affected. Post-2013, the rule applies a presumption that any impermissible acquisition, access, use, or disclosure of PHI is a breach unless the covered entity demonstrates through a risk assessment that there is a low probability the PHI was compromised.

Definition of Breach — §164.402

What Constitutes a Breach

A breach is the 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.

Presumption of Breach

Under the 2013 Omnibus Rule, an impermissible use or disclosure of PHI is presumed to be a breach unless the covered entity or business associate demonstrates through a four-factor risk assessment that there is a low probability that the PHI has been compromised.

Four-Factor Risk Assessment — §164.402(2)
FactorAssessment Questions
1. Nature and extent of PHI involvedWhat types of identifiers and clinical information were involved? Does the PHI include sensitive data (SSN, financial, substance abuse, mental health, HIV)? How many data elements were exposed?
2. Unauthorized person who used or received the PHIWho impermissibly accessed the PHI? Was it an unauthorized employee, an external attacker, an unintended recipient? Does the person have obligations to protect PHI (e.g., another covered entity)?
3. Whether the PHI was actually acquired or viewedWas the PHI actually accessed or viewed, or was there only an opportunity for access? Are there forensic logs demonstrating whether data was exfiltrated? Was an encrypted laptop stolen but the encryption verified as NIST-compliant?
4. Extent to which the risk has been mitigatedWere satisfactory assurances obtained from the recipient that the PHI will not be further used or disclosed? Was the PHI recovered? Was the recipient a covered entity that has agreed to destroy the information?

If the risk assessment demonstrates low probability of compromise across all four factors, the incident is not a breach and notification is not required. The assessment must be documented regardless of the conclusion.

Exceptions to the Breach Definition — §164.402(1)

Three circumstances are excluded from the definition of breach:

  1. Unintentional good-faith acquisition: PHI acquired unintentionally by a workforce member or person acting under the authority of the covered entity or BA, made in good faith and within the scope of authority, and the PHI is not further used or disclosed impermissibly
  2. Inadvertent disclosure between authorized persons: PHI inadvertently disclosed by a person authorized to access PHI to another person authorized to access PHI at the same covered entity, BA, or organized healthcare arrangement, and the information is not further used or disclosed impermissibly
  3. Good-faith belief of non-retention: The covered entity or BA has a good-faith belief that the unauthorized person to whom the disclosure was made would not reasonably have been able to retain the information

Unsecured PHI — §164.402

Breach notification obligations apply only to "unsecured PHI" — PHI that has not been rendered unusable, unreadable, or indecipherable to unauthorized individuals through one of the technologies specified by HHS:

Safe Harbor Technologies (HHS Guidance, 74 FR 19006)
TechnologySpecification
EncryptionNIST-validated encryption processes consistent with NIST Special Publication 800-111 (data at rest) and FIPS 140-2/140-3 validated modules. AES-128 or AES-256 for data at rest; TLS 1.2+ for data in transit
DestructionPaper: shredding or destruction such that PHI cannot be read or reconstructed. Electronic media: clearing, purging, or destroying consistent with NIST SP 800-88 Rev. 1

If PHI was properly encrypted and the encryption key was not compromised, or if PHI was properly destroyed, then it is "secured" and the breach notification provisions do not apply.

Notification Requirements

Individual Notification — §164.404

Who must notify: The covered entity (not the business associate directly, unless delegated by the BA agreement).

Timeframe: Without unreasonable delay, and no later than 60 calendar days from the date of discovery of the breach. Discovery occurs on the first day the breach is known or, by exercising reasonable diligence, would have been known. Knowledge of a workforce member or agent is imputed to the covered entity.

Method: Written notice by first-class mail to the individual's last known address (or next of kin if deceased). Email is permitted if the individual has agreed to electronic notice. If contact information is insufficient or out of date for 10 or more individuals, a conspicuous posting on the covered entity's website for 90 days or a notice in major print or broadcast media is required.

Content requirements (§164.404(c)):

  1. A brief description of what happened, including the date of the breach and the date of discovery
  2. A description of the types of unsecured PHI involved (e.g., name, SSN, date of birth, diagnosis, treatment information — do not include the actual PHI)
  3. Steps individuals should take to protect themselves from potential harm
  4. A brief description of what the covered entity is doing to investigate, mitigate harm, and prevent future breaches
  5. Contact procedures including a toll-free telephone number, email address, postal address, or website

Asclepius Health Network Individual Notice Template:

Asclepius Health Network maintains pre-approved breach notification letter templates reviewed by legal counsel, with variable fields for breach-specific details. The template includes:

  • Description of the incident
  • Types of information involved
  • Steps Asclepius has taken (investigation, remediation, enhanced safeguards)
  • Offer of complimentary credit monitoring and identity theft protection services (24 months for breaches involving SSN or financial data)
  • Toll-free call center number staffed by trained representatives
  • Instructions for placing fraud alerts and security freezes
  • Contact information for the Asclepius Privacy Office, HHS OCR, and relevant state attorney general
Show full SKILL.md (762 more words)Show less
HHS Secretary Notification — §164.408
Breach SizeReporting RequirementTimeframeMethod
500+ individualsIndividual report to HHSWithout unreasonable delay, no later than 60 days from discovery (concurrent with individual notification)HHS breach reporting portal (ocrportal.hhs.gov)
Fewer than 500 individualsLog and report annuallyWithin 60 days of end of calendar year in which breach was discoveredHHS breach reporting portal — annual breach log submission

Breaches affecting 500 or more individuals are posted on the HHS "Wall of Shame" — the public breach reporting portal at ocrportal.hhs.gov/ocr/breach/breach_report.jsf.

HHS Portal Required Fields:

  • Covered entity name, address, contact information
  • Covered entity type (health plan, healthcare provider, healthcare clearinghouse, BA acting as agent)
  • Number of individuals affected
  • Date of breach, date of discovery
  • Type of breach (hacking/IT incident, unauthorized access/disclosure, theft, loss, improper disposal, other)
  • Location of breached information (email, electronic medical record, network server, paper/films, laptop, desktop, portable device, other)
  • Type of PHI involved
  • Description of breach
  • Safeguards in place at time of breach
  • Actions taken in response
State Attorney General Notification — §13402(e)(3) HITECH

For breaches affecting 500 or more residents of a state or jurisdiction, the covered entity must notify the state attorney general concurrent with individual notification.

Asclepius Health Network operates across 4 states. If a breach affects 500+ residents of any single state, the AG of that state must be notified. Many states have their own breach notification laws with additional requirements; Asclepius tracks requirements across all 50 states and files notifications as required.

Media Notification — §164.406

For breaches affecting 500 or more residents of a state or jurisdiction, the covered entity must provide notice to prominent media outlets serving the state or jurisdiction without unreasonable delay and no later than 60 days from discovery. This is typically accomplished through a press release distributed to major media outlets in the affected area.

Business Associate Breach Obligations — §164.410

Business associates must:

  1. Notify the covered entity of a breach without unreasonable delay and no later than 60 days from discovery (or shorter if specified in the BAA)
  2. Identify affected individuals to the extent possible
  3. Provide information the covered entity needs to fulfill its notification obligations

The covered entity retains responsibility for individual, HHS, state AG, and media notification unless the BAA delegates notification to the BA. Asclepius Health Network BAAs require BA breach notification within 5 business days of discovery and require the BA to bear notification costs when the breach results from the BA's acts or omissions.

Breach Response Timeline — Asclepius Health Network

DayActionResponsible Party
Day 0Incident detected or reportedWorkforce member, IT security, BA
Day 0-1Incident response team activated; containment initiatedCISO, Incident Response Team
Day 1-7Forensic investigation; scope and nature of PHI determinedForensic investigators (internal or third-party)
Day 7-14Four-factor risk assessment completed; breach determination madePrivacy Officer, Legal Counsel
Day 14-21If breach confirmed: notification letters drafted, reviewed by legal, call center preparedPrivacy Office, Legal, Communications
Day 21-30Notification letters mailed; HHS portal submission preparedPrivacy Office, Compliance
Day 30-45HHS notified; state AG notified (if 500+ in a state); media notified (if 500+ in a state)Compliance, Legal
Day 45-60Substitute notice posted if needed; call center operational; credit monitoring enrollment trackedPrivacy Office, Vendor Management
Within 60 daysAll individual notifications completed (hard deadline)Privacy Office
OngoingRemediation measures implemented; risk analysis updated; workforce re-trainedCISO, Privacy Office, Training

Documentation Requirements — §164.414(b)

Covered entities must maintain documentation of breach risk assessments, notifications, and related actions for a minimum of 6 years from the date of creation or the date when the document was last in effect, whichever is later. This includes:

  • Breach risk assessment and determination
  • Individual notification copies and mailing records
  • HHS notification records
  • State AG notification records
  • Media notification records
  • Remediation documentation
  • Workforce sanctions applied

Enforcement Actions for Breach Notification Failures

  • Presence Health (2017): $475,000 — delayed breach notification by over 100 days beyond the 60-day deadline for breach affecting 836 individuals
  • Cottage Health (2019): $3 million — failure to conduct thorough risk assessment prior to breach; inadequate security measures contributing to breach of 62,500 records
  • Lafourche Medical Group (2023): $480,000 — phishing breach affecting approximately 34,862 individuals; failure to conduct risk analysis and implement security measures; late breach notification

Integration Points

  • hipaa-privacy-rule: Breach is defined as impermissible use/disclosure under the Privacy Rule
  • hipaa-security-rule: Security safeguards determine whether PHI is "unsecured" for notification purposes
  • hipaa-risk-analysis: Post-breach risk analysis update required; breach risk assessment is related but distinct from Security Rule risk analysis
  • hipaa-baa-management: BAA breach notification provisions define BA obligations
  • hitech-act-privacy: HITECH established the breach notification requirement and penalty tiers

© 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-notify 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 Notify 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.

Hipaa Breach Notify compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Hipaa Breach Notify this skillmukul975/Privacy-Data-Protection-Skills301—~3.4kAutomated safety check: PassApache-2.0
HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed5.5k—~1.7kAutomated safety check: PassApache-2.0
HIPAA Pre-Deployment Compliance Checkmaziyarpanahi/openmed5.5k—~2kAutomated safety check: PassApache-2.0
Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance9461 repos~2.3kAutomated safety check: PassMIT
ISO Standards Readiness EvidenceK-Dense-AI/scientific-agent-skills48k1 repos~4.6kAutomated safety check: NotesMIT
Fda Consultant Specialistdavila7/claude-code-templates33k1 repos~2.7kAutomated safety check: PassMIT

Similar skills

  • Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.

    5.5k GitHub stars~1.7k tokensUpdated yesterday
    Legal & ComplianceAuto-check passed
  • Walks a data pipeline against the HIPAA Privacy and Security Rule checklist and produces a gap report before it processes patient data.

    5.5k GitHub stars~2k tokensUpdated yesterday
    Legal & ComplianceAuto-check passed
  • Hipaa Compliance

    Sushegaad/Claude-Skills-Governance-Risk-and-Compliance

    Expert HIPAA compliance assistant for healthcare and software contexts.

    946 GitHub starsUsed in 1 repo~2.3k tokens
    Legal & ComplianceAuto-check passed
  • 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.

    48k GitHub starsUsed in 1 repo~4.6k tokens
    Legal & ComplianceAuto-check: notes
  • Fda Consultant Specialist

    davila7/claude-code-templates

    Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.

    33k GitHub starsUsed in 1 repo~2.7k tokens
    Legal & ComplianceAuto-check passed
  • 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…

    184 GitHub stars~6.1k tokensUpdated 4 days ago
    Legal & ComplianceAuto-check passed

More from mukul975/Privacy-Data-Protection-Skills

All 280 skills in this repo
  • Age Gating Services

    mukul975/Privacy-Data-Protection-Skills

    Implements age-gating mechanisms for online services to restrict access based on user age.

    301 GitHub stars~3.7k tokensUpdated 6 mo ago
    Auto-check passed
  • AI Data Retention

    mukul975/Privacy-Data-Protection-Skills

    Manages AI model retention and machine unlearning requirements.

    301 GitHub stars~1.9k tokensUpdated 6 mo ago
    Auto-check passed
  • 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.

    301 GitHub stars~3.4k tokensUpdated 6 mo ago
    Auto-check passed
  • 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).

    301 GitHub stars~846 tokensUpdated 6 mo ago
    Auto-check passed
  • 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.

    301 GitHub stars~1.9k tokensUpdated 6 mo ago
    Auto-check passed
  • 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.

    301 GitHub stars~880 tokensUpdated 6 mo ago
    Auto-check passed

Questions about Hipaa Breach Notify

What does Hipaa Breach Notify do?

Implements HIPAA breach notification requirements under 45 CFR §164.400-414. Hipaa Breach Notify is an agent skill from mukul975/Privacy-Data-Protection-Skills.400-414.

When should I use Hipaa Breach Notify?

Hipaa Breach Notify fits situations like: tasks that involve Healthcare and finance regulation.

How do I install Hipaa Breach Notify in Claude Code?

Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill hipaa-breach-notify -a claude-code`. Or copy the skill folder (skills/privacy/hipaa-breach-notify in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/hipaa-breach-notify in your project. Claude Code loads it when a task matches its description.

How do I install Hipaa Breach Notify in Codex?

Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill hipaa-breach-notify -a codex`. Or copy the skill folder (skills/privacy/hipaa-breach-notify in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/hipaa-breach-notify in your project. Codex loads it when a task matches its description.

Can I use Hipaa Breach Notify 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-notify -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-notify, .gemini/skills/hipaa-breach-notify, .github/skills/hipaa-breach-notify and .opencode/skills/hipaa-breach-notify in your project.

What does Hipaa Breach Notify need to run?

Going by SKILL.md and its folder, Hipaa Breach Notify needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Hipaa Breach Notify 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 Notify 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 Notify use?

Hipaa Breach Notify 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 Notify use?

About 3.4k tokens (SKILL.md is roughly 13k 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.4k tokens, read only when the agent opens those files.

What are the alternatives to Hipaa Breach Notify?

Skills that share tags, products or a category with Hipaa Breach Notify: 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 Notify?

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.