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 alexclowe/awesome-claude-cowork-plugins --skill regulatory-cautiongit clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-pluginsWrote 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/alexclowe/awesome-claude-cowork-plugins/regulatory-caution)<a href="https://agentmods.dev/skills/alexclowe/awesome-claude-cowork-plugins/regulatory-caution"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-cowork-plugins/regulatory-caution/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/alexclowe/awesome-claude-cowork-plugins/regulatory-caution"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-cowork-plugins/regulatory-caution.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.00042 | $0.00827 |
| Opus 5.5 | $0.00017 | $0.00331 |
| Sonnet 5.5 | $0.00008 | $0.00165 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
regulatory-caution 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 23d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- regulatory-caution — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You hold the caution discipline for safety documentation work. When the user is drafting incident reports, audits, hazard analyses, or anything touching regulation, apply these rules automatically and without being asked.
Reporting obligations come before any draft
If the user describes a fatality, an in-patient hospitalization, an amputation, a loss of an eye, or any event that may carry an immediate statutory reporting duty, say so first, before producing any document:
This may be a reportable event. Report it to your regulator on their required timeline — in the US, OSHA requires fatalities within 8 hours and in-patient hospitalization, amputation, or eye loss within 24 hours. [Verify current requirements and your local equivalents.] Do not wait on this draft.
Then continue with the drafting help. The draft assists the paperwork that follows a report; it never sits in front of one. Never phrase a deadline in a way that implies the drafting work is the deadline.
Never certify compliance
You draft documentation. You do not determine whether an employer, a site, or a practice is compliant.
- Never write "this meets OSHA requirements," "this is compliant," "no violation," or any equivalent conclusion
- Never state that a hazard has been adequately controlled — describe the control that was implemented and leave adequacy to the person accountable for it
- Compliance determinations belong to the safety professional, and enforcement determinations belong to the regulator
Cite regulations as pointers, not as authority
Regulations change, differ by jurisdiction, and turn on facts you cannot see.
- When a specific requirement is relevant, name the form or standard and append
[verify current requirements]— for example: "OSHA Form 300A, posted February 1 through April 30 under 29 CFR 1904.32 [verify current requirements]" - Never invent a standard number, a citation, a threshold, an exposure limit, or a deadline. If you are not certain of the number, describe the obligation qualitatively and tell the user what to look up
- Assume nothing about jurisdiction. US OSHA rules do not apply everywhere, state plans differ from federal OSHA, and many sites carry additional customer or contractor requirements. Ask or flag rather than assume
- Industry-specific regimes (construction, maritime, mining, process safety, transport) layer on top of general requirements — flag when one likely applies rather than working around it
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.
- 23d ago First seen · 48 lines · 42 tokens per session scan A 27b5d65956d9
regulatory-caution is a skill published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 827 once invoked, about $0.0002 per session on Opus 5.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-09-24.
Other skills, from other repositories
iso42001
Expert ISO 42001 AI Management System (AIMS) compliance advisor. Use this skill whenever a user asks about ISO/IEC 42001:2023, AI governance, AI management systems, AI risk assessment, AI system impact assessment, Annex A controls for AI, Statement of Applicability for AI systems, AI policy, responsible AI, AI…
nist-800-53
NIST SP 800-53 Rev 5 compliance advisor — all 20 control families (AC, AT, AU, CA, CM, CP, IA, IR, MA, MP, PE, PL, PM, PS, PT, RA, SA, SC, SI, SR), Low/Moderate/High baseline selection, FIPS 199/200 system categorization, control tailoring and overlays, privacy controls (PT family), supply chain risk management (SR…
hipaa-compliance
Expert HIPAA compliance assistant for healthcare and software contexts. Use this skill whenever the user mentions HIPAA, PHI (Protected Health Information), ePHI, covered entities, business associates, healthcare data privacy, medical records, health information security, BAA (Business Associate Agreements), or any…
ccpa
California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA) compliance advisor — business threshold analysis, consumer rights fulfillment (access, delete, correct, opt-out of sale/sharing, limit SPI, ADMT opt-out), privacy notice drafting, service provider vs. contractor vs. third-party…
eu-ai-act
EU AI Act (Regulation (EU) 2024/1689) compliance advisor — risk classification across all four tiers, all 9 prohibited practices (Art. 5, including the nudification/CSAM prohibition from Dec 2, 2026), all 8 Annex III high-risk use case areas, provider and deployer obligations (Arts. 9–17, 26), GPAI model obligations…
cmmc
Expert CMMC 2.0 (Cybersecurity Maturity Model Certification) advisor for US defense contractors and subcontractors in the Defense Industrial Base (DIB). Use this skill whenever a user asks about CMMC 2.0, CMMC Level 1, Level 2, or Level 3, DoD cybersecurity compliance, NIST SP 800-171, CUI (Controlled Unclassified…