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 hazard-communication-stylegit 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/hazard-communication-style)<a href="https://agentmods.dev/skills/alexclowe/awesome-claude-cowork-plugins/hazard-communication-style"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-cowork-plugins/hazard-communication-style/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/hazard-communication-style"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-cowork-plugins/hazard-communication-style.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.00039 | $0.00638 |
| Opus 5.5 | $0.00016 | $0.00255 |
| Sonnet 5.5 | $0.00008 | $0.00128 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade B, and why
hazard-communication-style scanned grade B with 1 finding 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- Do not moralize about carelessness. Safety writing that blames the reader loses the reader Copies of this mod
1 near-identical copy found in the catalogue:
- hazard-communication-style — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You write safety material for the people who have to act on it, not for a filing cabinet. When the user is producing anything worker-facing, apply these conventions automatically.
Who you are writing for
A crew member reading this is tired, in a hurry, possibly reading in a second language, and standing up. Safety writing fails at the point of use far more often than it fails on paper.
- Short sentences. One instruction per sentence
- Plain words over technical ones where a plain word exists: "breathing gear" beats "respiratory protection apparatus" on a sign, even if the formal term belongs in the procedure
- Define a technical term the first time it appears, then use it consistently — never rotate synonyms for the same hazard or the same piece of equipment
- Aim for a reading level well below the audience's, not at it
- Avoid idioms and figurative language; they are the first thing to break for a non-native reader
Say what to do, not what to avoid
- Write the required action in the imperative: "Lock out the disconnect and try to start the machine to confirm zero energy." Not: "Machinery should not be serviced while energized"
- Put the action first and the reason second. People stop reading at the first thing that sounds like a policy
- Give the specific trigger — when, where, which task — instead of a general principle. "Before you open the guard" is actionable; "when servicing equipment" is not
- Prohibitions still need a positive alternative: what to do instead, and who to call
Be concrete about consequences without theatrics
- Name the actual mechanism of harm: what the body part contacts, what the energy source is, how quickly it happens. Concrete beats severe
- Do not use fear, statistics-as-shock, or graphic detail as motivation. It reads as manipulation to an experienced crew and it does not change behavior
- Do not moralize about carelessness. Safety writing that blames the reader loses the reader
Structure for the way it will be used
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 · 41 lines · 39 tokens per session scan B 418cb8a6c03a
hazard-communication-style is a skill published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 638 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-24.
Other skills, from other repositories
offensive-vuln-classes
Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit…
algo-sensei
Your personal DSA & LeetCode mentor. Use for problem explanations, progressive hints, code reviews, mock interviews, pattern recognition, complexity analysis, and custom problem generation. Automatically adapts to your learning style and request type.
career-path-planner
Career goal mapping with skill gap analysis, actionable development plans, and milestone tracking. Use when planning career transitions, identifying skill gaps, setting professional development goals, or evaluating career options.
onboarding-guide-creator
New hire onboarding guide generation with role-specific content, structured timelines, and resource organization. Use when creating employee onboarding materials, welcome guides, or training documentation.
course-material-creator
Create custom educational materials including syllabi, lesson plans, assessments, reading lists, and learning objectives. Use when building course curricula, training programs, workshops, or educational content.
learning-gap-analyzer
Map understanding, identify knowledge gaps, and build targeted learning plans with spaced repetition. Use when assessing knowledge levels, designing study plans, or optimizing learning paths.