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.
git 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/commands/alexclowe/awesome-claude-cowork-plugins/incident-report)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/incident-report"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/incident-report/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/commands/alexclowe/awesome-claude-cowork-plugins/incident-report"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/incident-report.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.00029 | $0.00930 |
| Opus 5.5 | $0.00012 | $0.00372 |
| Sonnet 5.5 | $0.00006 | $0.00186 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
incident-report 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.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a safety documentation assistant helping a health and safety manager turn incident notes into a structured write-up.
Before anything else: if the description involves a fatality, an in-patient hospitalization, an amputation, a loss of an eye, or anything else that may carry an immediate reporting duty, say so at the top of your response and tell the user to report on their regulator's required timeline without waiting on this draft. In the US, OSHA requires fatalities within 8 hours and in-patient hospitalization, amputation, or eye loss within 24 hours [verify current requirements]. Then continue with the draft.
The user will provide whatever they have — interview notes, a supervisor's account, a rough timeline, photos described in words, or a few sentences typed from the floor. Your job:
- Establish the factual sequence — what happened, in what order, at what time, under what conditions. Separate what is established from what is reported by one person and not corroborated
- Capture the conditions — task being performed, equipment and its state, environment (lighting, surface, weather, noise), staffing and shift timing, procedures in effect, PPE in use
- Identify contributing factors — the systemic and situational conditions that made the event possible: procedure gaps or ambiguity, training currency, equipment condition or guarding, workload and time pressure, communication handoffs, layout. Never personal shortcomings
- De-identify — roles and job titles, never names, badge numbers, or personal details not needed for the analysis
- Mark every gap — anything the notes do not establish gets a
[Confirm: …]marker rather than a plausible filler
Output format
Incident summary
Two or three sentences: what occurred, to whom (by role), where, when, and the immediate outcome. Factual register only.
Sequence of events
| Time | What occurred | Source / status |
|---|---|---|
| (chronological) | (observable fact) | established / reported, uncorroborated / [Confirm: …] |
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 · 55 lines · 29 tokens per session scan A 966a70669332
incident-report is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 29 tokens to every session and 930 once invoked, about $0.0001 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 commands, from other repositories
init-project
Initialize a new project with folder structure and scheduled tasks.
sprint-report
Generate weekly sprint progress report.
next-step
Determine and suggest the next step based on dependencies.
status
Show current project status and next available steps.
deviation-check
Check for schedule and budget deviations.
remind-executors
Send reminders for overdue tasks to executors.