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 shortage-impact-mapgit 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/shortage-impact-map)<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/shortage-impact-map"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/shortage-impact-map/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/shortage-impact-map"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/shortage-impact-map.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.00084 | $0.00669 |
| Opus 5.5 | $0.00034 | $0.00268 |
| Sonnet 5.5 | $0.00017 | $0.00134 |
| Haiku 4.5 | $0.00008 | $0.00067 |
Grade A, and why
shortage-impact-map 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shortage Impact Map
Purpose
Deterministically explode the shortage: net the short part's usable on-hand and the incoming (late) PO against every open order that consumes it, and produce a per-order impact row (product, line, order, need-by, quantity at risk, status) plus a rolled-up impact summary (worst severity + the first-impact date). This is the mapping the whole packet turns on.
When to use
- After supply-knowledge-retrieve, in every run.
- "Which lines and orders does this shortage hit, and when does it bite?".
Inputs
- The contract payload with
supply{}(on_hand, on_order, safety_stock),promised_date,revised_dateandretrieved.open_orders[](contractmfg.supplier-disruption.v1).
Steps
- Validate the payload against the contract.
- Run
scripts/shortage_impact_map.py --intake disruption-intake.json --out impact-map.json. - Do not restate or re-derive the netting in prose; quote the engine output verbatim.
- Emit the
{impact_map, impact_summary}contract payload and the preliminarynext_best_action.
Output
Contract mfg.supplier-disruption.v1 with a populated impact_map[] (per-order status + qty at risk)
and impact_summary{} (worst_severity, first_impact_date, affected products/orders, total qty at
risk, below_safety_stock, confidence, source=engine:shortage_impact_map) — the {impact} hop.
Grounding requirements
The netting and per-order status cite references/impact-mapping-rules.md #3-#4; the first-impact
date cites #5; the summary cites #6.
Constraints
- All mapping logic happens in the engine. The model must never decide the impact or the dates itself.
- The incoming (late) PO only covers orders whose need-by is on/after the revised date (impact-mapping-rules.md #2) — do not credit it earlier.
- Never drop a
late_shipment(customer order at risk) to make the picture look better — it is the reason a case is critical.
Escalation / uncertainty
- Incomplete MRP position (missing open orders, on-hand or revised date) or a below-safety-stock
projection: the engine adds to
escalations[]; surface it and confirm the netting in the ERP before a mitigation is committed (impact-mapping-rules.md #7).
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
- scripts/shortage_impact_map.py 7.3 KB runs code
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 · 53 lines · 84 tokens per session scan A e43e9ddc9df9
shortage-impact-map is a skill published in the GitHub repository microsoft/cat-agent-skills (93 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 669 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.