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 Cleo-Labs-IA/skills_library --skill product-safety-incidentgit clone --depth 1 https://github.com/Cleo-Labs-IA/skills_libraryWrote 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/cleo-labs-ia/skills_library/product-safety-incident)<a href="https://agentmods.dev/skills/cleo-labs-ia/skills_library/product-safety-incident"><img src="https://agentmods.dev/badge/skills/cleo-labs-ia/skills_library/product-safety-incident/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/cleo-labs-ia/skills_library/product-safety-incident"><img src="https://agentmods.dev/badge/skills/cleo-labs-ia/skills_library/product-safety-incident.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.00061 | $0.03571 |
| Opus 5 | $0.00030 | $0.01785 |
| Sonnet 5 | $0.00012 | $0.00714 |
| Haiku 4.5 | $0.00006 | $0.00357 |
Grade A, and why
product-safety-incident 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Safety Incident Response
Step-by-step protocol from detection of a product safety issue to case closure. Time-critical: missed notification deadlines = criminal liability in most jurisdictions.
Incident Response Flow
digraph {
rankdir=TB; node [shape=box style=rounded fontsize=10];
detect [label="1. DETECT\nCustomer complaint, QC fail,\nauthority notice, media report"];
triage [label="2. TRIAGE (24h)\nIs this a safety issue?\nSeverity assessment"];
contain [label="3. CONTAIN (24-48h)\nSales stop, quarantine stock,\nwarehouse hold"];
assess [label="4. RISK ASSESS\nSeverity x Probability\nmatrix"];
notify_auth [label="5. NOTIFY AUTHORITIES\nCPSC 24h / Safety Gate 10 days\n/ OPSS"];
notify_chain [label="6. NOTIFY SUPPLY CHAIN\nDistributors, retailers,\nmarketplaces"];
action [label="7. CORRECTIVE ACTION\nRecall / repair / refund /\nwarning / modification"];
notify_consumer [label="8. NOTIFY CONSUMERS\nDirect + public notice"];
rca [label="9. ROOT CAUSE ANALYSIS\nWhy + how to prevent"];
close [label="10. CLOSE\nEffectiveness check +\nfinal report"];
detect -> triage -> contain -> assess -> notify_auth -> notify_chain -> action -> notify_consumer -> rca -> close;
}
Step 1: Detection Sources
| Source | Typical Signal | Urgency |
|---|---|---|
| Customer complaint | Injury report, burn, allergic reaction, electric shock, choking near-miss | IMMEDIATE if injury |
| Quality control | Batch test failure, contamination found, wrong component | HIGH -- assess scope |
| Market surveillance authority | RAPEX/Safety Gate alert, CPSC notification, OPSS contact | HIGH -- authority expects response |
| Competitor/media | Social media report, press article, competitor product recall (same component) | MEDIUM -- investigate |
| Internal discovery | Design flaw found, supplier non-conformance, test report discrepancy | MEDIUM -- assess impact |
| Distributor/retailer | Return spike, complaint pattern, marketplace flag | MEDIUM-HIGH |
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.
- 12d ago First seen · 274 lines · 61 tokens per session scan A 406b90d9880c
product-safety-incident is a skill published in the GitHub repository Cleo-Labs-IA/skills_library (1 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 3,571 once invoked, about $0.0003 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.
Other skills, from other repositories
hipaa-validate
HIPAA validator: PHI exposure, audit logging, encryption, access control, BAA refs. Triggers: HIPAA, PHI, healthcare compliance, audit log, BAA.
standards-expert
Expert-level ISO standards, quality management, compliance, and certification. Use when the user mentions ISO standards, quality management, compliance, or certification, or when the task involves Compliance & Certification, Auditing, or Continuous Improvement.
soc2-expert
Expert in SOC 2 compliance, trust service criteria, audit preparation, controls implementation, and security frameworks. Use when the user mentions compliance, audit, trust services, AICPA, controls, or security framework, or when the task involves Trust Service Criteria, SOC 2 Types, Security Common Criteria, or…
lawyer-expert
Expert-level legal systems, contracts, compliance, and legal technology. Use when the user mentions legal, contracts, compliance, law, or legal tech, or when the task involves Legal Systems, Legal Technology, Compliance Frameworks, or Contract Management.
audit-expert
Expert-level security auditing, compliance, code review, and vulnerability assessment. Use when the user mentions compliance, security review, code review, vulnerability assessment, SOC 2, or GDPR, or when the task involves Audit Types, Audit Frameworks, Audit Process, or Authentication Review.
hr-payroll
Help HR operations specialists, payroll administrators, and compensation teams understand, design, and run payroll processing, compliance, and payroll-related HR operations. Use when asked to set up a payroll process, run a payroll compliance audit, design a payroll calendar, handle a payroll discrepancy, build a…