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.
Maintains the GDPR Article 33(5) breach register documenting all personal data breaches regardless of whether supervisory authority notification was required.
Install Breach Documentation
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill breach-documentation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills breach-documentation --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/breach-documentation .claude/skills/breach-documentation && 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 "breach-documentation" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/breach-documentation into .claude/skills/breach-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "breach-documentation", 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/breach-documentationType 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 breach-documentation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills breach-documentation --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/breach-documentation .agents/skills/breach-documentation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "breach-documentation" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/breach-documentation into .agents/skills/breach-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "breach-documentation", 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 breach-documentation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills breach-documentation --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/breach-documentation .cursor/skills/breach-documentation && 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 "breach-documentation" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/breach-documentation into .cursor/skills/breach-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "breach-documentation", 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/breach-documentation--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 breach-documentation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills breach-documentation --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/breach-documentation .gemini/skills/breach-documentation && 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 "breach-documentation" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/breach-documentation into .gemini/skills/breach-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "breach-documentation", 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 breach-documentationInstalls 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 breach-documentation -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/breach-documentation .github/skills/breach-documentation && 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 "breach-documentation" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/breach-documentation into .github/skills/breach-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "breach-documentation", 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 breach-documentation -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 breach-documentation --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/breach-documentation .opencode/skills/breach-documentation && 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 "breach-documentation" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/breach-documentation into .opencode/skills/breach-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "breach-documentation", 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
breach-documentation- GitHub stars
- 295
- Token cost
- ~2.4k tokens
- SKILL.md length
- 1,118 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 278
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Maintains the GDPR Article 33(5) breach register documenting all personal data breaches regardless of whether supervisory authority notification was required.
- Works in 4 steps: Instant availability: The register must… → Completeness verification: Monthly… → Cross-reference integrity: Each register… → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Mandatory Documentation…, Notification Decision… and Register Structure and…, plus 3 more sections
- Runs Python scripts from its folder
What it does
Breach Documentation is an agent skill from mukul975/Privacy-Data-Protection-Skills. Maintains the GDPR Article 33(5) breach register documenting all personal data breaches regardless of whether supervisory authority notification was required. Covers mandatory register fields including facts, effects, and remedial actions, retention periods, audit readiness, and integration with the accountability framework. Keywords: breach register, Article 33(5), breach documentation, accountability, audit readiness, remedial actions.
Its SKILL.md is about 2.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 Privacy and GDPR and Audit readiness. 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 Privacy and GDPR
- Tasks that involve Audit readiness
Example prompts
- “Use the breach-documentation skill to maintain the GDPR Article 33(5) breach register documenting all personal data breaches regardless of whether…”
- “/breach-documentation”
Requirements
- Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Instant availability: The register must be exportable in a structured format (CSV, JSON, PDF) within 24 hours of a supervisory authority…
- Completeness verification: Monthly self-audit to verify all reported security incidents were assessed for personal data impact and, where…
- Cross-reference integrity: Each register entry must link to supporting documentation (risk assessment form, SA notification copy, DS…
- Trend reporting: The register must support generation of trend reports showing: breach frequency over time, breach types, root cause…
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
Breach Documentation loads about 2.4k tokens when it runs, and up to ~4.4k if it reads all its reference files. Until then it costs about 116 tokens; SKILL.md has 1,118 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,118 words, ~2,397 tokens.
Download SKILL.mdSave it as
.claude/skills/breach-documentation/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- breach-documentation
- description
- Maintains the GDPR Article 33(5) breach register documenting all personal data breaches regardless of whether supervisory authority notification was required. Covers mandatory register fields including facts, effects, and remedial actions, retention periods, audit readiness, and integration with the accountability framework. Keywords: breach register, Article 33(5), breach documentation, accountability, audit readiness, remedial actions.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- data-breach-response
- metadata.tags
- breach-register, article-33-5, documentation, accountability, audit, remedial-actions
Maintaining Breach Documentation Records
Overview
Article 33(5) of the GDPR requires every controller to document all personal data breaches, regardless of whether the breach triggered supervisory authority notification. The documentation must include "the facts relating to the personal data breach, its effects and the remedial action taken" and must "enable the supervisory authority to verify compliance with this Article." This creates a comprehensive breach register that serves as a primary accountability document under Art. 5(2).
Mandatory Documentation Requirements — Art. 33(5)
Facts Relating to the Breach
Every breach register entry must document:
| Field | Description | Example |
|---|---|---|
| Breach reference number | Unique sequential identifier | SPG-BREACH-2026-003 |
| Discovery date and time | UTC timestamp when controller became aware | 13 March 2026, 14:30 UTC |
| Breach date and time | UTC timestamp of the breach itself (if different from discovery) | 13 March 2026, 11:15 UTC |
| Breach type | Confidentiality, integrity, availability, or combined | Availability (primary), Confidentiality (under investigation) |
| Breach description | Factual narrative of what occurred | LockBit 3.0 ransomware encrypted production customer database cluster. Attack vector: compromised service account obtained via spear-phishing. |
| Affected systems | Systems involved in the breach | db-prod-eu-west-01 through db-prod-eu-west-04 |
| Data subject categories | Types of individuals affected | Individual account holders, business account holders, joint account holders |
| Data subject count | Approximate number of affected individuals | 15,230 |
| Personal data categories | Types of data compromised | Names, postal addresses, emails, payment card last-4, transaction histories, account balances |
| Record count | Approximate number of affected records | 48,720 |
| Root cause | Identified cause of the breach | Stale privileged service account + phishing + push-fatigue MFA bypass |
| Containment timestamp | When the breach was contained | 13 March 2026, 12:45 UTC |
Effects of the Breach
| Field | Description | Example |
|---|---|---|
| Risk assessment score | Aggregate score from the risk assessment methodology | 18/24 |
| Risk level | Resulting risk determination | Approaching high risk |
| Actual harm identified | Any confirmed harm to data subjects | No confirmed harm as of assessment date |
| Potential harm | Likely consequences if data is misused | Financial fraud, identity theft, targeted phishing |
| Duration of impact | How long data subjects were affected | 36 hours (database unavailability); ongoing (potential confidentiality impact) |
Remedial Actions Taken
| Field | Description | Example |
|---|---|---|
| Containment measures | Immediate actions to stop the breach | Network isolation, credential revocation, backup restoration |
| Remediation measures | Longer-term corrective actions | MFA upgrade to FIDO2, service account lifecycle management, network segmentation |
| Remediation status | Current status of each action | 4 of 7 measures completed; 3 in progress |
| Remediation deadline | Target completion date | 15 June 2026 |
Notification Decision Documentation
Every breach entry must also record the notification decision and rationale:
| Field | Description |
|---|---|
| Art. 33 SA notification decision | Required / Not required |
| Art. 33 notification rationale | Why notification was or was not required (reference risk assessment) |
| Art. 33 notification date | Date and time of SA notification (if applicable) |
| SA reference number | Reference number assigned by the supervisory authority |
| SA follow-up status | Any follow-up inquiries or actions from the authority |
| Art. 34 DS notification decision | Required / Not required / Exempt under Art. 34(3) |
| Art. 34 notification rationale | Why DS notification was or was not required |
| Art. 34 notification date | Date of DS communication (if applicable) |
| Art. 34 notification method | Channels used (email, postal, public communication) |
Register Structure and Maintenance
Single Centralized Register
All breaches must be recorded in a single centralized register maintained by the DPO's office. Stellar Payments Group uses a dedicated module in the OneTrust Privacy Management Platform with the following access controls:
- Write access: DPO, Deputy DPO, Privacy Incident Coordinator
- Read access: CISO, General Counsel, Internal Audit, Board Audit Committee
- No access: Business unit managers, IT operations staff (access to individual breach records provided on a need-to-know basis via separate reports)
All Breaches Documented — Including Non-Notifiable
The register must include every personal data breach, regardless of severity or whether SA/DS notification was triggered. This explicitly includes:
- Misdirected emails containing personal data (even single-recipient incidents)
- Temporary availability breaches resolved from backup
- Unsuccessful exfiltration attempts where personal data was targeted but not accessed
- Breaches at processors that affected the controller's data
- Physical breaches (lost devices, unauthorized office access)
Show full SKILL.md (470 more words)Show less
Retention Period
Breach register entries are retained for a minimum of 7 years from the date of breach closure. This accounts for:
- The 5-year statute of limitations for GDPR enforcement actions in most EU member states
- The need to demonstrate patterns (or absence of patterns) to supervisory authorities
- Litigation time limits for data subject compensation claims under Art. 82
After the 7-year retention period, entries are anonymized (data subject counts retained, specific identifiers removed) and maintained indefinitely for trend analysis.
Audit Readiness
Supervisory Authority Access — Art. 33(5)
The breach register must be available to the supervisory authority "on request." Audit readiness requires:
- Instant availability: The register must be exportable in a structured format (CSV, JSON, PDF) within 24 hours of a supervisory authority request.
- Completeness verification: Monthly self-audit to verify all reported security incidents were assessed for personal data impact and, where applicable, added to the register.
- Cross-reference integrity: Each register entry must link to supporting documentation (risk assessment form, SA notification copy, DS notification copy, investigation report, remediation evidence).
- Trend reporting: The register must support generation of trend reports showing: breach frequency over time, breach types, root cause categories, notification rates, and remediation completion rates.
Annual Breach Register Review
The DPO conducts an annual review of the breach register covering:
- Completeness: Are all known breaches documented? Cross-reference against the security incident management system.
- Accuracy: Sample 20% of entries and verify accuracy against source documentation.
- Timeliness: Were entries created within 72 hours of breach discovery?
- Remediation closure: Are remediation actions tracked to completion? Flag overdue actions.
- Pattern identification: Are there recurring breach types or root causes indicating systemic issues?
- Board reporting: Prepare an annual breach summary report for the Board Audit Committee.
Integration with Other Records
| Related Record | Integration Point |
|---|---|
| Art. 30 RoPA | Link affected processing activities to the breach entry |
| DPIA Register | Update DPIAs for affected processing activities with breach as risk event |
| Vendor Register | Update processor risk assessment if breach originated at a processor |
| Training Records | Document post-breach training delivered to relevant personnel |
| Audit Log | Reference internal audit findings related to the breach |
| Insurance Records | Link to cyber insurance claim reference (if applicable) |
Common Documentation Deficiencies
- Breaches documented in security incident systems but not in the Art. 33(5) register: The security incident ticket is not a substitute for the breach register entry.
- Missing notification decision rationale: Recording "not notified" without documenting why the breach was assessed as unlikely to result in risk.
- Incomplete remediation tracking: Remedial actions listed but never updated to reflect completion status.
- Delayed documentation: Entries created weeks after the breach, making it difficult to demonstrate timely awareness and response.
- No processor breach entries: Breaches that occur at processors but affect the controller's data are not recorded in the controller's register.
© 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/breach-documentation 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
Breach Documentation 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 |
|---|---|---|---|---|---|---|
| Breach Documentation this skillmukul975/Privacy-Data-Protection-Skills | 295 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Compliance Osalirezarezvani/claude-skills | 28k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Implementing Complianceancoleman/ai-design-components | 526 | — | ~4k | Automated safety check: Pass | MIT | |
| Compliance Checklistmohitagw15856/pm-claude-skills | 1.4k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Compliance Checklist Generationseb1n/awesome-ai-agent-skills | 206 | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
Compliance Os
alirezarezvani/claude-skills
Compliance OS — meta-orchestrator that lets compliance teams CONFIGURE which frameworks apply, COMPUTE cross-framework control overlap, SIMULATE internal audits, and CONSOLIDATE evidence across…
Implementing Compliance
ancoleman/ai-design-components
Implement and maintain compliance with SOC 2, HIPAA, PCI-DSS, and GDPR using unified control mapping, policy-as-code enforcement, and automated evidence collection.
Compliance Checklist
mohitagw15856/pm-claude-skills
Generate a prioritised compliance checklist for GDPR, SOC 2, ISO 27001, FCA, HIPAA, or other frameworks with a gap analysis.
Compliance Checklist Generation
seb1n/awesome-ai-agent-skills
Build evidence-oriented readiness checklists for frameworks such as SOC 2, HIPAA, PCI DSS, and GDPR, with gaps and remediation priorities.
C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
More from mukul975/Privacy-Data-Protection-Skills
All 278 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.
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.
Retention Schedule
mukul975/Privacy-Data-Protection-Skills
Designs and implements data retention schedules compliant with GDPR Article 5(1)(e) storage limitation principle.
Related
Categories
Questions about Breach Documentation
What does Breach Documentation do?
Maintains the GDPR Article 33(5) breach register documenting all personal data breaches regardless of whether supervisory authority notification was required. Breach Documentation is an agent skill from mukul975/Privacy-Data-Protection-Skills. Maintains the GDPR Article 33(5) breach register documenting all personal data breaches regardless of whether supervisory authority notification was required.
When should I use Breach Documentation?
Breach Documentation fits situations like: tasks that involve Privacy and GDPR; tasks that involve Audit readiness.
How do I install Breach Documentation in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill breach-documentation -a claude-code`. Or copy the skill folder (skills/privacy/breach-documentation in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/breach-documentation in your project. Claude Code loads it when a task matches its description.
How do I install Breach Documentation in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill breach-documentation -a codex`. Or copy the skill folder (skills/privacy/breach-documentation in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/breach-documentation in your project. Codex loads it when a task matches its description.
Can I use Breach Documentation 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 breach-documentation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/breach-documentation, .gemini/skills/breach-documentation, .github/skills/breach-documentation and .opencode/skills/breach-documentation in your project.
What does Breach Documentation need to run?
Going by SKILL.md and its folder, Breach Documentation needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Breach Documentation 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 Breach Documentation 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 Breach Documentation use?
Breach Documentation 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 Breach Documentation use?
About 2.4k tokens (SKILL.md is roughly 9.6k 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 2k tokens, read only when the agent opens those files.
What are the alternatives to Breach Documentation?
Skills that share tags, products or a category with Breach Documentation: HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), Compliance Os (alirezarezvani/claude-skills, 28k stars), Implementing Compliance (ancoleman/ai-design-components, 526 stars) and Compliance Checklist (mohitagw15856/pm-claude-skills, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Breach Documentation?
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 295 GitHub stars. The repository holds 278 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.