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-intakegit 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-intake)<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/disruption-intake"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/disruption-intake/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-intake"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/disruption-intake.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.00088 | $0.00757 |
| Opus 5.5 | $0.00035 | $0.00303 |
| Sonnet 5.5 | $0.00018 | $0.00151 |
| Haiku 4.5 | $0.00009 | $0.00076 |
Grade A, and why
disruption-intake 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Disruption Intake
Purpose
Turn a supply disruption arriving from any channel — a PO/ERP record, a shipment (ASN) feed, a supplier email, or a portal notice — into structured contract inputs: the disruption identity, the short/delayed part, the supplier and PO, the promised vs revised date, the short quantity, the reason, and the trigger channel. This is the entry payload every later skill builds on.
When to use
- "A PO is late" / "our supplier is delayed" / "we're short on a part" / "process this supplier notice".
- A disruption signal arrives by PO record, shipment feed, supplier email or portal notice.
- Start of any Supplier Disruption Agent run.
Inputs
- The disruption signal in any channel: PO/ERP record (CSV/JSON), shipment/ASN feed (CSV), supplier email (TXT), or portal notice (TXT).
- Emits inputs for contract
mfg.supplier-disruption.v1.
Steps
- Identify the trigger channel and set
trigger_channel(po_record | shipment_feed | supplier_email | portal_notice) anddisruption_type(late_po | shipment_delay | shortage | supplier_notice). - Extract the anchor into
supplier,po_number,supplier_or_po, and the short/delayedpart{}(part_no,description,uom). - Capture
promised_date,revised_date,short_qty,reasonandreported_at. When the supplier text downplays the delay but a feed/portal shows a worse date, record the worse, evidenced date — never soften a date the data does not support. - Write the factual account into
description. - Produce
disruption-intake.jsonwithcontract_version,disruption_id,supplier_or_po, the fields above, and emptysupply{},retrieved{},history{}for the retrieval skill to fill.
Output
disruption-intake.json conforming to the contract inputs — the entry payload of the flow.
Grounding requirements
Every extracted fact cites its source (PO row, ASN line, email line, or portal notice). The revised date cites the feed/portal record, not just the supplier's prose.
What ships with it
6 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 · 58 lines · 88 tokens per session scan A bc50e856f782
disruption-intake is a skill published in the GitHub repository microsoft/cat-agent-skills (93 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 757 once invoked, about $0.0004 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.