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 supply-knowledge-retrievegit 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/supply-knowledge-retrieve)<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/supply-knowledge-retrieve"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/supply-knowledge-retrieve/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/supply-knowledge-retrieve"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/supply-knowledge-retrieve.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.00101 | $0.00763 |
| Opus 5.5 | $0.00040 | $0.00305 |
| Sonnet 5.5 | $0.00020 | $0.00153 |
| Haiku 4.5 | $0.00010 | $0.00076 |
Grade A, and why
supply-knowledge-retrieve 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.
Supply Knowledge Retrieve
Purpose
Enrich the disruption payload with grounded supply context: the ERP/MRP position for the part (on-hand, on-order, safety stock, lead time), the supplier master (single-source flag, approved alternates, substitutes), the BOM/where-used mapping and the open production/sales orders that consume the part, and the supplier's on-time delivery history (to reveal a chronic pattern).
When to use
- After disruption-intake, in every run.
- "Where is this part used and what's our on-hand?" / "has this supplier been late before?".
Inputs
disruption-intake.json(contract inputs from disruption-intake).- ERP inventory/MRP export (CSV): part, on_hand, on_order, safety_stock, lead_time_days.
- Supplier master (CSV): single_source, alternate suppliers + lead times, approved substitutes.
- BOM/where-used (CSV): parent product, component, per-unit qty, line.
- Open orders (CSV): order_id, type (production/sales), product, finished_qty, need_by, customer.
- Supplier on-time history (CSV): prior POs, promised vs actual, days late.
Steps
- Populate
supply{}:on_hand,on_order(the delayed PO qty),safety_stock,lead_time_days,single_source,substitutes[](withapproved+available_qty),alternates[](withlead_time_days+qualified). - Explode the BOM/where-used and join to open orders into
retrieved.open_orders[]: each withorder_type,product,line,finished_qty,per_unit,need_by,customer,high_runner. - Populate
history{}:window_days,late_count,on_time_pct,prior_shipments[], and setchronic_pattern = truewhen the supplier is repeatedly late (a systemic signal). - Attach supplier master + sourcing standards into
retrieved{}, each with a citation.
Output
The contract payload with populated supply{}, retrieved{} and history{} — the input to
shortage-impact-map.
Grounding requirements
Every open order cites its order record; every supply figure cites the ERP/master export; every prior shipment cites its PO row.
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 · 101 tokens per session scan A 744b1c4fa229
supply-knowledge-retrieve is a skill published in the GitHub repository microsoft/cat-agent-skills (93 stars, last pushed today), licensed MIT. It adds 101 tokens to every session and 763 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.