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 mitigation-recommendgit 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/mitigation-recommend)<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/mitigation-recommend"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/mitigation-recommend/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/mitigation-recommend"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/mitigation-recommend.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.00082 | $0.00665 |
| Opus 5.5 | $0.00033 | $0.00266 |
| Sonnet 5.5 | $0.00016 | $0.00133 |
| Haiku 4.5 | $0.00008 | $0.00067 |
Grade A, and why
mitigation-recommend 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.
Mitigation Recommend
Purpose
Deterministically choose the mitigation — expedite, substitute or reschedule — from the impact summary and the supply position (substitutes, alternate suppliers, lead time, single-source flag, supplier history), set the urgency, build the cumulative owner-notification list, and raise the governance escalations — then finalize the recommended next-best action.
When to use
- After shortage-impact-map, in every run.
- "Should we expedite or substitute, and who do we escalate to?".
Inputs
- The contract payload with
impact_summary{}(worst_severity, first_impact_date, total qty at risk) andsupply{}(substitutes, alternates, single_source) andhistory.chronic_pattern(contractmfg.supplier-disruption.v1).
Steps
- Validate the payload against the contract.
- Run
scripts/mitigation_recommend.py --impact impact-map.json --out disruption-packet.json. - Do not restate or recompute the mitigation choice or the escalations in prose; quote the engine output verbatim.
- Emit the
{mitigation, notifications}contract payload and the finalizednext_best_action.
Output
Contract mfg.supplier-disruption.v1 with a populated mitigation{} (option, urgency, actions,
substitute_part/alternate_supplier, confidence, source=engine:mitigation_recommend), a
notifications[] owner list, and appended escalations[] plus the finalized next_best_action —
the {mitigation} hop.
Grounding requirements
The mitigation choice cites references/mitigation-escalation-rules.md #1; the urgency cites #2; each
escalation cites #3; each notification cites #4.
Constraints
- All mitigation/escalation logic happens in the engine. The model must never choose the mitigation or escalate itself.
- Draft-first: the plugin drafts the mitigation and notifications; it never expedites, substitutes, reschedules or emails on its own. A buyer/planner confirms.
- Never suppress a customer-order (late_shipment) escalation or a chronic-supplier escalation because of time pressure.
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/mitigation_recommend.py 12 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 · 57 lines · 82 tokens per session scan A e65a78107e74
mitigation-recommend is a skill published in the GitHub repository microsoft/cat-agent-skills (93 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 665 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.