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 criticality-rankgit 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/criticality-rank)<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/criticality-rank"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/criticality-rank/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/criticality-rank"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/criticality-rank.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.00073 | $0.00526 |
| Opus 5.5 | $0.00029 | $0.00210 |
| Sonnet 5.5 | $0.00015 | $0.00105 |
| Haiku 4.5 | $0.00007 | $0.00053 |
Grade A, and why
criticality-rank 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
Criticality Rank
Purpose
Deterministically compute the maintenance priority (P1-P4), response target, and downtime cost for the fault from the asset-criticality matrix, escalating for recurring failures.
When to use
- After failure-mode-rank, in every triage run.
- "How urgent is this?" / "what's the priority?" / "what does downtime cost?".
Inputs
- The contract payload with
ranked_causes[],asset_criticality,downtime_cost_per_hr, andhistory.repeat_promotion(contractmfg.maintenance-triage.v1, the{ranked_causes}hop).
Steps
- Validate the payload against the contract.
- Run
scripts/criticality_score.py --ranked ranked-causes.json --out triaged.json. - Do not restate or recompute any score in prose; quote the engine output verbatim.
- Emit the
{priority}contract payload and therecommended_action.
Output
Contract mfg.maintenance-triage.v1 with a populated priority{} object (level, score,
response_target, downtime_cost_estimate, factors, confidence,
source=engine:criticality_score, citation) — the {priority} hop.
Grounding requirements
Every priority cites the matrix sections used and ISO 55000 risk-based prioritization
(references/asset-criticality-matrix.md, references/rcm-iso55000-excerpts.md).
Constraints
- All scoring math happens in the engine. The model must never set a priority itself.
- Never downgrade a repeat-failure escalation to save a planned-outage slot.
- Do not draft the work order here — that is work-order-update's job.
Escalation / uncertainty
- Missing downtime cost yields an estimated impact and an escalation; a P1 assignment or a repeat-failure escalation is surfaced to the shift supervisor and planner (asset-criticality-matrix.md #6).
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.maintenance-triage.v1.json 628 B
- contracts/plugin-mfg.maintenance-triage.v1.json 5.0 KB
- references/asset-criticality-matrix.md 2.9 KB
- references/failure-mode-library.md 3.9 KB
- references/rcm-iso55000-excerpts.md 2.1 KB
- scripts/criticality_score.py 5.6 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 · 50 lines · 73 tokens per session scan A f4b4ff584b33
criticality-rank is a skill published in the GitHub repository microsoft/cat-agent-skills (93 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 526 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.