breach-notification

breach-notification is a skill for Claude Code from bromso/metapowers. It costs 11 tokens per session (1,283 once invoked), scanned A, original, MIT.

A process for checking what notices are required after a data breach, organized by location and contract. A data breach is unauthorized access to or disclosure of protected information.

In plain words
What is it for?
It assesses breach-notification duties by jurisdiction, including GDPR requirements, reviews contractual deadlines, and produces a decision tree and reusable notice templates when the required scope files exist.
Why use it?
It helps determine who must be notified, what the notice must contain, and which deadlines or contractual service targets apply.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the compliance plugin — 12 skills, 1 MCP server shipped together

Good fit It assesses breach-notification duties by jurisdiction, including GDPR requirements, reviews contractual deadlines, and produces a decision tree and reusable notice templates when the required scope files exist.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bromso/metapowers/breach-notification
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add bromso/metapowers --skill breach-notification
Clone the repo
git clone --depth 1 https://github.com/bromso/metapowers

Made for: Claude Code.

Or install compliance, the plugin that ships this one along with the rest of its 12 skills, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for breach-notification

README.md
[![agentmods](https://agentmods.dev/badge/skills/bromso/metapowers/breach-notification.svg)](https://agentmods.dev/skills/bromso/metapowers/breach-notification)
Your own site
<a href="https://agentmods.dev/skills/bromso/metapowers/breach-notification"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/breach-notification.svg" alt="Measured on agentmods" height="20"></a>
Per session 11 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,283 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00011 $0.01283
Opus 5 $0.00005 $0.00642
Sonnet 5 $0.00002 $0.00257
Haiku 4.5 $0.00001 $0.00128

Measured 8d ago against content hash da7194dbdbb4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

breach-notification scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/compliance/skills/breach-notification/SKILL.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Breach Notification Compliance Assessment

Assess breach notification compliance for "$ARGUMENTS". Map notification requirements by jurisdiction, evaluate contractual SLA obligations, and create a notification decision tree and template library.

Prerequisites

Read .metapowers/compliance/$ARGUMENTS/00-scope.md. If this file does not exist, tell the user:

Phase 0 (Scope) has not been completed for "$ARGUMENTS". Run /compliance:regulatory-landscape $ARGUMENTS first, or use --skip-checks to bypass.

If --skip-checks is present in $ARGUMENTS, skip this check.

Process

  1. Read context files:

    • Read plugins/compliance/shared/grc-lifecycle-guide.md for GRC methodology reference
    • Read plugins/compliance/shared/assessment-template.md for output structure
    • Read .metapowers/compliance/$ARGUMENTS/00-scope.md for scope and control framework context
  2. GDPR breach notification (Art 33-34):

    • Assess notification to supervisory authority procedures (72-hour timeline from awareness)
    • Evaluate notification content requirements (nature of breach, categories/numbers affected, DPO contact, consequences, measures taken)
    • Review notification to data subjects procedures (without undue delay if high risk to rights and freedoms)
    • Assess breach severity assessment methodology (risk to individuals determination)
    • Evaluate cross-border notification procedures (lead supervisory authority identification)
    • Review breach record-keeping obligations (all breaches, not just notifiable ones)
  3. US state breach notification laws:

    • Map notification requirements across all applicable states
    • Assess state-specific timelines (varies 30-90 days; some states have specific deadlines: Colorado 30 days, Florida 30 days, Washington 30 days)
    • Evaluate Attorney General notification thresholds per state (e.g., 500+ individuals in many states)
    • Review definition of "personal information" variations by state (some include login credentials, biometrics, health data)
    • Assess consumer reporting agency notification requirements (typically 1,000+ individuals)
    • Evaluate encryption and redaction safe harbors by state
    • Review content requirements for notification letters per state

Read the full file on GitHub · 104 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 104 lines · 11 tokens per session scan A da7194dbdbb4

Subscribe to this mod's changes

breach-notification is a skill published in the GitHub repository bromso/metapowers (1 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 1,283 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

internal-controls-and-audit

Designs and tests controls over financial reporting — segregation of duties, approval limits, evidence, and preparing for audit. Use this to design controls for a process, prepare for an external audit, respond to an audit finding, set approval thresholds, or assess where a small team's segregation of duties is…

cbrock84/headcount · 67 tokens

chief-legal-and-risk-officer

Owns legal, contracts, intellectual property, regulatory compliance, privacy, security governance, enterprise risk, and audit readiness. Use this to review a contract or commitment, assess regulatory or privacy exposure, evaluate an IP or licensing question, judge the risk in a business decision, prepare for an audit…

cbrock84/headcount · 98 tokens

intellectual-property

Covers what the organization owns and what it is only borrowing — trademarks and clearance, copyright and work-for-hire, patents and trade secrets, open-source license obligations and copyleft reach, and IP terms in customer, contractor and AI-tool agreements. Use this to check whether a name is usable, establish that…

cbrock84/headcount · 91 tokens

chief-human-resources-officer

Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations. Use this to design or restructure a team, plan hiring, write a role or leveling definition, handle a performance or compensation question, diagnose why a team is underperforming for non-technical…

cbrock84/headcount · 90 tokens

deal-negotiation

Negotiates a commercial deal without giving away the terms that matter — preparing your walk-away and theirs, trading concessions rather than conceding them, recognizing the tactics that create false urgency, protecting price by moving other variables, and closing on terms someone can actually deliver. Use this to…

cbrock84/headcount · 91 tokens

capital-structure-and-covenants

Decides how the business is financed and what that financing then requires of it — debt versus equity, weighted average cost of capital as a hurdle rate, how much leverage cash flow can carry, and the financial, affirmative and negative covenants, definitions, test dates and cure rights that come attached. Use this to…

cbrock84/headcount · 102 tokens