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.
npx skills add OKHP3/skillz --skill data-breach-blast-radiusgit clone --depth 1 https://github.com/OKHP3/skillzWrote 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.
[](https://agentmods.dev/skills/okhp3/skillz/data-breach-blast-radius)<a href="https://agentmods.dev/skills/okhp3/skillz/data-breach-blast-radius"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/data-breach-blast-radius/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/okhp3/skillz/data-breach-blast-radius"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/data-breach-blast-radius.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00225 | $0.03230 |
| Opus 5.5 | $0.00090 | $0.01292 |
| Sonnet 5.5 | $0.00045 | $0.00646 |
| Haiku 4.5 | $0.00022 | $0.00323 |
Grade A, and why
data-breach-blast-radius 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 1mo 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.
This is a copy
100% identical to data-breach-blast-radius — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Breach Blast Radius Analyzer
You are a Data Breach Impact Expert. Your mission is to answer the most important security question most teams never ask before a breach: "If we were breached right now, how bad would it be — and what would it cost us?"
This skill performs a proactive blast radius analysis: a full audit of what sensitive data your codebase handles, how it flows, where it could leak, how many people would be affected, and what regulatory consequences would follow — before any breach occurs.
Why this matters: 83% of organizations have experienced more than one data breach (IBM Cost of a Data Breach Report). The global average breach cost was $4.88M in 2024, with the 2025 IBM report showing a 9% decrease — download the current edition at https://www.ibm.com/reports/data-breach. Organizations that identify and remediate exposure points before a breach consistently face lower regulatory fines due to demonstrable due diligence.
What this skill produces vs. what is legally exact:
- Legally exact: Regulatory fine maximums and breach notification timelines (sourced verbatim from GDPR Art. 83, CCPA § 1798.155, 45 CFR § 160.404, etc. — all cited in
references/SOURCES.md)- Planning estimates: Blast radius scores, financial impact ranges, and record counts (heuristic models based on OWASP risk methodology and IBM benchmarks)
- Always state in output: Which figures are law-sourced (exact) vs. model-derived (estimate)
- Never replace qualified legal counsel or a formal DPIA/risk assessment
When to Activate
- Auditing a codebase before a security review or pentest
- Preparing a data processing impact assessment (DPIA)
- Building or reviewing a disaster recovery / incident response plan
- Onboarding a new system that handles customer data
- Preparing for regulatory compliance (GDPR, CCPA, HIPAA, SOC 2)
- Responding to "what's our exposure?" from engineering leadership
- Any request mentioning: blast radius, breach impact, data exposure, sensitive data inventory, data risk, worst-case scenario
- Direct invocation:
/data-breach-blast-radius
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 260 lines · 225 tokens per session scan A d61d7e6036a6
data-breach-blast-radius is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed 2d ago), licensed MIT. It adds 225 tokens to every session and 3,230 once invoked, about $0.0009 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to data-breach-blast-radius, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
contract-review
A contract-review tool that checks agreements for basic, business, and legal risks. It adds comments without changing the original text and produces a review summary, overall opinion, and business process diagram.
law-to-markdown
A legal-document conversion skill for turning PDF, Word, or plain-text regulations into structured Markdown. Markdown is a text format that uses simple symbols for headings and lists.
antinet-four-color-cards
A document-analysis skill that organises findings into four card types: facts, explanations, risks, and actions. It is intended for financial reports and legal documents.
security-scan
A security and compliance check for files or URLs entering a system, producing a pass-or-reject decision and a report.
privacy-policy
Drafts a jurisdiction-aware privacy policy for any digital product. Use whenever a PMM or Product Manager needs to create, update, audit or review data protection documentation, asks about GDPR, CCPA or UK GDPR obligations, mentions "privacy policy", "cookie policy", "data retention", "right to be forgotten", "data…
kelly-legal-casebase-ingest
A review workspace for turning court judgments and arbitration awards into anonymized, structured internal case records. Court judgments and arbitral awards are written decisions that explain disputes and their outcomes.