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 disruption-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/disruption-writeup)<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/disruption-writeup"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/disruption-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/disruption-writeup"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/disruption-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.00080 | $0.00696 |
| Opus 5.5 | $0.00032 | $0.00278 |
| Sonnet 5.5 | $0.00016 | $0.00139 |
| Haiku 4.5 | $0.00008 | $0.00070 |
Grade A, and why
disruption-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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Disruption Write-up
Purpose
Produce the human-readable artifacts: a supplier follow-up (chasing the late PO / requesting the
expedite / confirming the revised date) and an internal escalation brief (impact + mitigation +
owners + decision needed), rendered from templates/disruption-writeup-template.md and populated only
from the contract payload — the disruption context, the impact summary and map, the mitigation, the
owner notifications, the escalations and the recommended next-best action.
When to use
- After mitigation-recommend, to close the loop.
- "Draft the supplier follow-up" / "write the escalation brief".
Inputs
disruption-packet.json(contractmfg.supplier-disruption.v1, the{mitigation}hop withimpact_map[],impact_summary{},mitigation{},notifications[],next_best_action,escalations[]).
Steps
- Validate input against the contract.
- Fill
templates/disruption-writeup-template.md: disruption identification, the impact summary + per-order impact map table, the mitigation block, the owner-notification list, a visible "Open items / escalations" block, the recommended next-best action, the drafted supplier follow-up (references/supplier-comms-standards.md#1-#2) and the drafted internal escalation brief (#3). - Render to the requested format (markdown; DOCX/PDF via the platform document component).
- Choose the audience voice: buyer, production planner, or materials manager.
- Mark the write-up DRAFT — pending buyer/planner review and sign-off.
Output
DISR-<disruption_id>-writeup.md (or .docx) — the terminal artifact of the contract flow.
Grounding requirements
The impact traces to engine:shortage_impact_map; the mitigation and escalations trace to
engine:mitigation_recommend; the drafting standards cite supplier-comms-standards.md.
Constraints
- Draft-first: no PO placed/expedited, no ERP or schedule write, no email sent, and no supplier commitment in v1. The write-up is a recommendation, not an executed action.
- Nothing appears in the write-up that is not present in the contract payload.
- A customer-order (late_shipment) risk and its first-impact date 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.
- assets/LICENSE.txt 1.0 KB
- contracts/mfg.supplier-disruption.v1.json 9.2 KB
- references/impact-mapping-rules.md 4.8 KB
- references/mitigation-escalation-rules.md 4.8 KB
- references/sourcing-standards-excerpts.md 3.5 KB
- references/supplier-comms-standards.md 3.0 KB
- templates/disruption-writeup-template.md 3.8 KB
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 · 57 lines · 80 tokens per session scan A ad5737716b98
disruption-writeup is a skill published in the GitHub repository microsoft/cat-agent-skills (93 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 696 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.