Prior Art Scout
n1m21n/Infinite
Find publicly documented solutions (peer repos, GitHub, forums) to bugs, platform quirks, dependency gotchas or architectural patterns, respecting the copyleft discussions-only rule.
Conducts structured post-breach remediation using a lessons learned framework covering root cause remediation, control gap closure, policy updates, training modifications, monitoring enhancements…
Install Breach Remediation
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill breach-remediation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills breach-remediation --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-remediation .claude/skills/breach-remediation && 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-remediation" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/breach-remediation into .claude/skills/breach-remediation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "breach-remediation", 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-remediationType 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-remediation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills breach-remediation --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-remediation .agents/skills/breach-remediation && 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-remediation" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/breach-remediation into .agents/skills/breach-remediation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "breach-remediation", 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-remediation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills breach-remediation --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-remediation .cursor/skills/breach-remediation && 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-remediation" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/breach-remediation into .cursor/skills/breach-remediation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "breach-remediation", 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-remediation--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-remediation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills breach-remediation --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-remediation .gemini/skills/breach-remediation && 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-remediation" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/breach-remediation into .gemini/skills/breach-remediation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "breach-remediation", 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-remediationInstalls 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-remediation -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-remediation .github/skills/breach-remediation && 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-remediation" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/breach-remediation into .github/skills/breach-remediation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "breach-remediation", 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-remediation -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-remediation --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-remediation .opencode/skills/breach-remediation && 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-remediation" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/breach-remediation into .opencode/skills/breach-remediation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "breach-remediation", 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-remediation- GitHub stars
- 301
- Token cost
- ~2.3k tokens
- SKILL.md length
- 1,040 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Conducts structured post-breach remediation using a lessons learned framework covering root cause remediation, control gap closure, policy updates, training modifications, monitoring enhancements…
- Works in 6 steps: Root Cause Remediation (Immediate —… → Control Gap Closure (Short-Term — Within… → Policy Updates (Medium-Term — Within 90… → …
- Tasks that involve Root cause analysis
- SKILL.md covers Overview, Lessons Learned Framework, Remediation Tracking and Post-Breach Review Meeting, plus 1 more section
- Runs Python scripts from its folder
What it does
Breach Remediation is an agent skill from mukul975/Privacy-Data-Protection-Skills. Conducts structured post-breach remediation using a lessons learned framework covering root cause remediation, control gap closure, policy updates, training modifications, monitoring enhancements, and regulatory follow-up. Provides a systematic approach to preventing breach recurrence and demonstrating accountability to supervisory authorities. Keywords: post-breach, remediation, lessons learned, root cause, control gap, policy update, training.
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 Root cause analysis and Privacy and GDPR. 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 Root cause analysis
- Tasks that involve Privacy and GDPR
Example prompts
- “Use the breach-remediation skill to conduct structured post-breach remediation using a lessons learned framework covering root cause remediation…”
- “/breach-remediation”
Requirements
- Python 3
Workflow steps
6 steps, taken from the step headings in SKILL.md.
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 Remediation loads about 2.3k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 117 tokens; SKILL.md has 1,040 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,040 words, ~2,321 tokens.
Download SKILL.mdSave it as
.claude/skills/breach-remediation/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- breach-remediation
- description
- Conducts structured post-breach remediation using a lessons learned framework covering root cause remediation, control gap closure, policy updates, training modifications, monitoring enhancements, and regulatory follow-up. Provides a systematic approach to preventing breach recurrence and demonstrating accountability to supervisory authorities. Keywords: post-breach, remediation, lessons learned, root cause, control gap, policy update, training.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- data-breach-response
- metadata.tags
- post-breach-remediation, lessons-learned, root-cause, control-gap, accountability
Conducting Post-Breach Remediation
Overview
Post-breach remediation transforms the findings from a breach investigation into concrete corrective actions that prevent recurrence and demonstrate accountability under GDPR Art. 5(2) and Art. 24. Effective remediation goes beyond fixing the immediate vulnerability — it addresses root causes, closes systemic control gaps, updates policies and training, enhances monitoring, and satisfies regulatory follow-up requirements.
Lessons Learned Framework
Step 1: Root Cause Remediation (Immediate — Within 30 Days)
Address the direct technical and procedural cause of the breach:
| Root Cause Category | Remediation Approach | Example (SPG-BREACH-2026-003) |
|---|---|---|
| Stale privileged account | Decommission account, implement lifecycle management | Revoked svc-migration-2024; deployed automated service account expiry (90-day review cycle) |
| Phishing vulnerability | Deploy phishing-resistant MFA, enhance email filtering | Migrated from push-based MFA to FIDO2/WebAuthn for all privileged accounts |
| Insufficient network segmentation | Implement micro-segmentation | Deployed database-tier isolation; access only via approved bastion host with session recording |
| Inadequate access review scope | Expand access review to include all account types | Added service accounts, API keys, and machine accounts to quarterly access certification |
Step 2: Control Gap Closure (Short-Term — Within 90 Days)
Identify and close broader security and privacy control gaps revealed by the breach:
- Detection gap: Was the breach detected by the organization's own controls, or was it reported externally? If detection was delayed, strengthen monitoring.
- Response gap: Were response procedures followed? Where did the team deviate from the plan? Update procedures based on actual experience.
- Communication gap: Were internal and external communications timely and accurate? Update communication templates and escalation matrices.
- Documentation gap: Were the Art. 33(5) documentation requirements met in real-time? Improve documentation tools and checklists.
- Vendor/processor gap: If a processor was involved, was the Art. 28 DPA adequate? Were processor security requirements sufficient? Update vendor risk assessment and DPA terms.
Step 3: Policy Updates (Medium-Term — Within 90 Days)
Review and update affected policies based on breach findings:
| Policy | Update Required | Owner | Deadline |
|---|---|---|---|
| Access Control Policy | Include service accounts in scope; define lifecycle management requirements | CISO | 15 April 2026 |
| Incident Response Plan | Update awareness definition; add holding statement template; revise escalation matrix | DPO + CISO | 30 April 2026 |
| Ransom Payment Policy | Document Board-approved position on ransom payments | General Counsel | 31 May 2026 |
| Vendor Risk Management | Add security assessment questionnaire updates based on processor breach lessons | Procurement + DPO | 30 June 2026 |
| Data Retention Policy | Verify that expired data was actually deleted per schedule (breach may have revealed retention failures) | DPO | 30 June 2026 |
Step 4: Training Modifications (Medium-Term — Within 90 Days)
Update training programs to address the human factors contributing to the breach:
| Training Module | Target Audience | Update | Delivery Method |
|---|---|---|---|
| Phishing awareness | All employees | Add scenario based on the actual phishing email that initiated SPG-BREACH-2026-003 (with identifying details removed) | Interactive simulation via KnowBe4 |
| MFA security | All employees with MFA | Add push-fatigue attack awareness; train on rejecting unexpected MFA prompts | Mandatory e-learning module |
| Incident reporting | All employees | Clarify that unusual system behavior must be reported immediately, even if uncertain | Updated in annual privacy awareness training |
| Breach response | Incident response team | Tabletop exercise based on this breach scenario | Semi-annual tabletop exercise |
| Privileged access management | IT operations, DBAs | Service account lifecycle management procedures | Department-specific workshop |
Step 5: Monitoring Enhancements (Medium-Term — Within 90 Days)
Strengthen detection and monitoring based on gaps the breach revealed:
| Enhancement | Description | Owner | Deadline |
|---|---|---|---|
| Service account anomaly detection | SIEM rule to alert when service accounts authenticate outside scheduled batch windows or from non-whitelisted IPs | SOC Lead | 15 April 2026 |
| MFA push-fatigue detection | Alert when an account receives more than 3 MFA push notifications in 5 minutes without successful authentication | SOC Lead | 30 April 2026 |
| Tor exit node blocking | Block authentication attempts from known Tor exit nodes for all production systems | Network Security | 15 April 2026 |
| Network flow baseline for database tier | Establish outbound data transfer baselines for database VLAN; alert on anomalies | SOC Lead | 31 May 2026 |
Show full SKILL.md (407 more words)Show less
Step 6: Regulatory Follow-Up (Ongoing)
Manage ongoing obligations to supervisory authorities:
- Supplementary notifications: Provide any outstanding information committed to in the initial Art. 33 notification (e.g., exfiltration determination, final data subject count).
- Authority inquiries: Respond promptly and comprehensively to any follow-up questions from the supervisory authority.
- Remediation evidence: Be prepared to provide evidence of remediation actions to the authority upon request. Maintain a remediation tracker with completion dates and evidence references.
- Regulatory proceedings: If the authority initiates formal proceedings, coordinate response with external counsel.
- Annual DPO report: Include the breach and remediation status in the DPO's annual report to the Board and supervisory authority.
Remediation Tracking
Remediation Register Structure
| Field | Description |
|---|---|
| Action ID | Unique identifier (SPG-BREACH-2026-003-REM-001) |
| Breach reference | Link to the source breach |
| Description | What needs to be done |
| Root cause addressed | Which root cause or gap this action closes |
| Owner | Person responsible for completion |
| Priority | Critical / High / Medium / Low |
| Target date | Planned completion date |
| Actual completion date | When the action was verified as complete |
| Evidence | Documentation proving completion (screenshot, policy version, test report) |
| Verified by | Person who verified the action was effectively implemented |
Escalation for Overdue Actions
| Days Overdue | Escalation |
|---|---|
| 1-7 days | Reminder to action owner |
| 8-14 days | Escalation to action owner's manager |
| 15-30 days | Escalation to DPO and CISO |
| 30+ days | Escalation to CEO; inclusion in Board Audit Committee report |
Post-Breach Review Meeting
Agenda (Conducted 30 Days After Breach Closure)
- Breach summary: 5-minute recap of the incident.
- Root cause review: Confirm root cause analysis is accurate and complete.
- Remediation status: Review all remediation actions — completed, in progress, overdue.
- Effectiveness assessment: Have the implemented remediations been tested and proven effective?
- Residual risk: What risk remains after remediation? Is it within the organization's risk appetite?
- Lessons for next time: What would we do differently? What worked well?
- Documentation closure: Confirm all Art. 33(5) documentation is complete.
Demonstrating Accountability
Under GDPR Art. 5(2), the controller must demonstrate compliance. Post-breach remediation evidence serves this purpose:
- Before the breach: Risk assessments, security measures, training records, and policies demonstrate preventive efforts.
- During the breach: Incident response documentation, notification records, and communication logs demonstrate responsive handling.
- After the breach: Remediation tracker, updated policies, enhanced controls, and improved training demonstrate learning and improvement.
A supervisory authority reviewing the organization's breach response will assess not only whether the breach was handled correctly but whether the organization took meaningful steps to prevent recurrence.
© 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-remediation 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 Remediation 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 Remediation this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Prior Art Scoutn1m21n/Infinite | 271 | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Repo Prepglebis/claude-skills | 391 | — | ~1.6k | Automated safety check: Pass | MIT | |
| C15tc15t/c15t | 1.9k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Korean Privacy Termskimlawtech/korean-privacy-terms | 587 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Repo Prep
glebis/claude-skills
Interactively prepare a code repository for publication — LICENSE, NOTICE, AUTHORSHIP, README sections, package metadata, .gitignore, community docs (CONTRIBUTING/CODEOFCONDUCT/SECURITY/CHANGELOG)…
C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
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.
Korean Privacy Terms
kimlawtech/korean-privacy-terms
처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). An agent skill from kimlawtech/korean-privacy-terms.
Gdpr Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert GDPR compliance assistant covering all four core workflows: (1) auditing code and systems for GDPR violations, (2) drafting GDPR-compliant documents such as privacy policies, Data Processing…
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 Breach Remediation
What does Breach Remediation do?
Conducts structured post-breach remediation using a lessons learned framework covering root cause remediation, control gap closure, policy updates, training modifications, monitoring enhancements…. Breach Remediation is an agent skill from mukul975/Privacy-Data-Protection-Skills. Conducts structured post-breach remediation using a lessons learned framework covering root cause remediation, control gap closure, policy updates, training modifications, monitoring enhancements, and regulatory follow-up.
When should I use Breach Remediation?
Breach Remediation fits situations like: tasks that involve Root cause analysis; tasks that involve Privacy and GDPR.
How do I install Breach Remediation in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill breach-remediation -a claude-code`. Or copy the skill folder (skills/privacy/breach-remediation in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/breach-remediation in your project. Claude Code loads it when a task matches its description.
How do I install Breach Remediation in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill breach-remediation -a codex`. Or copy the skill folder (skills/privacy/breach-remediation in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/breach-remediation in your project. Codex loads it when a task matches its description.
Can I use Breach Remediation 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-remediation -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-remediation, .gemini/skills/breach-remediation, .github/skills/breach-remediation and .opencode/skills/breach-remediation in your project.
What does Breach Remediation need to run?
Going by SKILL.md and its folder, Breach Remediation needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Breach Remediation 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 Remediation 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 Remediation use?
Breach Remediation 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 Remediation use?
About 2.3k tokens (SKILL.md is roughly 9.3k 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 1.1k tokens, read only when the agent opens those files.
What are the alternatives to Breach Remediation?
Skills that share tags, products or a category with Breach Remediation: Prior Art Scout (n1m21n/Infinite, 271 stars), Repo Prep (glebis/claude-skills, 391 stars), C15t (c15t/c15t, 1.9k stars) and HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Breach Remediation?
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.