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 parts-readinessgit 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/parts-readiness)<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/parts-readiness"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/parts-readiness/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/parts-readiness"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/parts-readiness.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.00079 | $0.00577 |
| Opus 5.5 | $0.00032 | $0.00231 |
| Sonnet 5.5 | $0.00016 | $0.00115 |
| Haiku 4.5 | $0.00008 | $0.00058 |
Grade A, and why
parts-readiness 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.
What it actually says
Parts Readiness
Purpose
Deterministically assemble the required parts for the work order, check each against storeroom stock and the supersession table, and compute an overall readiness status (READY, READY_WITH_SUBSTITUTION, PARTIAL, BLOCKED), escalating shortages and redirecting procurement for superseded parts.
When to use
- After similar-work-rank, in every run.
- "Are the parts in stock?" / "can we schedule this?" / "is that part still current?".
Inputs
- The contract payload with
required_parts[],parts_catalog[],superseding_fix{}andasset_criticality(contractmfg.work-order-assist.v1, the{similar_work}hop).
Steps
- Validate the payload against the contract.
- Run
scripts/parts_readiness.py --similar similar-work.json --out work-order-packet.json. - Do not restate or recompute any stock number in prose; quote the engine output verbatim.
- Emit the
{parts_readiness}contract payload and the finalizednext_best_action.
Output
Contract mfg.work-order-assist.v1 with a populated parts_readiness{} object (status, per-part
lines with line_status and effective_part, blockers, confidence, source=engine:parts_readiness,
citation) — the {parts_readiness} hop.
Grounding requirements
Every line cites its parts-catalog row; a supersession redirect cites
references/parts-readiness-rules.md #2; a critical-part block cites #3.
Constraints
- All readiness math happens in the engine. The model must never set a status itself.
- Never re-order a superseded part; redirect to its current replacement (parts-readiness-rules.md #2).
- Do not draft the write-up here — that is work-order-writeup's job.
Escalation / uncertainty
- A critical part out of stock (BLOCKED), a class-A asset shortage, or a superseded SOP part: the
engine adds to
escalations[]; surface the blockers so no un-executable job is scheduled (parts-readiness-rules.md #3).
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.
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 · 50 lines · 79 tokens per session scan A 123ce788bc6f
parts-readiness is a skill published in the GitHub repository microsoft/cat-agent-skills (93 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 577 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
netbox-reconcile
Reconcile NetBox source of truth against live network state - detect IP drift, missing interfaces, undocumented links, cable mismatches, VLAN mismatches, and ticket discrepancies in ServiceNow. Use when validating NetBox accuracy, checking for config drift, auditing network documentation, or reconciling source of…
equipment-fleet-manager
Manage construction equipment fleet. Track utilization, maintenance, and assignments.
tia-multiuser
TIA Portal Multiuser Engineering operations. Use for managing server projects, local sessions, and multiuser commissioning workflows.
biomass-power-plant-manager
Use when a task needs the judgment of a Biomass Power Plant Manager — running a biomass-fired power generation facility, managing fuel supply logistics and quality variability, evaluating combustion/efficiency problems, or balancing generation output against fuel cost and emissions constraints.
diptrace-production-pack
A workflow for preparing and inspecting a versioned manufacturing package for a DipTrace board. It brings together fabrication files such as Gerbers and drill files, assembly data, a bill of materials, instructions, and release evidence.
hw-product-owner
Hardware Product Owner role -- manages hardware requirements, BOM budgets, trade-offs between performance/cost/schedule, stakeholder communication, feasibility analysis, and make-vs-buy decisions for hardware projects.