microsoft/cat-agent-skills is a static website that catalogs reusable instruction sets and related packages for AI agents. People use it to search, filter, rate, and download skills for Cowork, Copilot Studio, and Scout, along with Copilot plugins and Scout automations. The catalogue entries are the skills, instructions, plugins, and settings displayed by the site.
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 microsoft/cat-agent-skills --skill incident-writeupgit clone --depth 1 https://github.com/microsoft/cat-agent-skillsWrote 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/microsoft/cat-agent-skills/incident-writeup)<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/incident-writeup"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/incident-writeup/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/microsoft/cat-agent-skills/incident-writeup"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/incident-writeup.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.00083 | $0.00655 |
| Opus 5.5 | $0.00033 | $0.00262 |
| Sonnet 5.5 | $0.00017 | $0.00131 |
| Haiku 4.5 | $0.00008 | $0.00065 |
Grade A, and why
incident-writeup 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 today.
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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Write-up
Purpose
Produce the human-readable artifact: an incident write-up rendered from
templates/incident-writeup-template.md, populated only from the contract payload — the incident
context, the classification (severity, recordable + column, reportable + clock), the routing and
notifications, the reporting checklist, the recommended next-best action, and a root-cause-analysis
template (5-Why; fishbone for high/critical).
When to use
- After routing-notify, to close the loop.
- "Draft the incident summary" / "give me the RCA template" / "prepare the OSHA write-up".
Inputs
incident-packet.json(contractmfg.safety-incident-assist.v1, the{routing}hop withclassification{},routing{},next_best_action,escalations[]).
Steps
- Validate input against the contract.
- Fill
templates/incident-writeup-template.md: incident identification, factual summary, the classification block, the routing & notification list, the regulatory clock, a visible "Open items / escalations" block, the recommended next-best action, and the RCA template (references/rca-standards-excerpts.md#4). - Render to the requested format (markdown; DOCX/PDF via the platform document component).
- Choose the audience voice: EHS manager, line supervisor, or plant manager.
- Mark the write-up DRAFT — pending EHS-owner review and sign-off.
Output
INC-<incident_id>-writeup.md (or .docx) — the terminal artifact of the contract flow.
Grounding requirements
The classification traces to engine:recordability_classify; the routing traces to
engine:routing_notify; OSHA/ISO/JHA references cite the reference files.
Constraints
- Draft-first: no OSHA filing, no auto-notification, and no incident closure in v1. The write-up is a recommendation, not an executed action — this preserves the reporting checklist and audit trail.
- Nothing appears in the write-up that is not present in the contract payload.
- A recordable/reportable determination and its regulatory clock must never be softened or hidden in the draft.
What ships with it
7 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.
- today First seen · 56 lines · 83 tokens per session scan A ba62781b77c8
incident-writeup is a skill published in the GitHub repository microsoft/cat-agent-skills (93 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 655 once invoked, about $0.0003 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-10-28.
Other skills, from other repositories
html-ppt-zhangzara-stencil-tablet
A workplace-safety compliance review for a manufacturing regulator — findings, the evidence chain, and the corrective mandate. Built as a decision-grade policy briefing deck for regulator, plant leadership.
treatment-plans
Formats and structurally validates local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
handbook-updates
Diff a proposed handbook change against the current version, flag ripple effects and state supplement impacts. Use when user says "update the handbook", "add this to the handbook", "handbook change", or has a policy ready for insertion.
terms-of-service
Draft terms of service and a companion privacy notice matched to the product's form and feature modules, not legal advice, delivered as a Word document.
software-copyright-materials
A workflow for creating Chinese application materials for software copyright registration from a real software project.