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 routing-notifygit 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/routing-notify)<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/routing-notify"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/routing-notify/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/routing-notify"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/routing-notify.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.00069 | $0.00580 |
| Opus 5.5 | $0.00028 | $0.00232 |
| Sonnet 5.5 | $0.00014 | $0.00116 |
| Haiku 4.5 | $0.00007 | $0.00058 |
Grade A, and why
routing-notify 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Routing & Notify
Purpose
Deterministically assign the investigator by severity (escalated one level on a repeat pattern), build the cumulative owner-notification list, start any OSHA reportability clock with a computed due-by, and raise the governance escalations — then finalize the recommended next-best action.
When to use
- After severity-recordability, in every run.
- "Who investigates this and who do we notify?" / "start the OSHA clock" / "route this incident".
Inputs
- The contract payload with
classification{}(severity, recordable, reportable + deadline) andhistory.repeat_pattern, plusoccurred_at(contractmfg.safety-incident-assist.v1).
Steps
- Validate the payload against the contract.
- Run
scripts/routing_notify.py --classification classification.json --out incident-packet.json. - Do not restate or recompute any assignment or clock in prose; quote the engine output verbatim.
- Emit the
{routing}contract payload and the finalizednext_best_action.
Output
Contract mfg.safety-incident-assist.v1 with a populated routing{} object (investigator,
notifications[], regulatory_clocks[], confidence, source=engine:routing_notify, citation) plus the
finalized next_best_action and appended escalations[] — the {routing} hop.
Grounding requirements
The investigator assignment cites references/routing-matrix.md #1; each notification cites #2; a
regulatory clock cites #3; escalations cite #4.
Constraints
- All routing/notification/clock logic happens in the engine. The model must never assign or notify itself.
- Draft-first: the plugin drafts the routing and notifications; it never auto-sends a notification or files an OSHA report. A human owner confirms (audit trail intact).
- Never drop or suppress a regulatory clock or a reportable escalation because of time pressure.
Escalation / uncertainty
- A reportable event, a recordable case, a repeat pattern, or low classification confidence: the
engine adds to
escalations[]; surface them so the clock and the sign-offs are visible (routing-matrix.md #4).
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 · 52 lines · 69 tokens per session scan A dd21caf6acf8
routing-notify is a skill published in the GitHub repository microsoft/cat-agent-skills (93 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 580 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
vendor-review
Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.
entity-compliance
Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30/60/90 days. Use when user says "entity…
portfolio
Track the IP portfolio — registrations, renewals, maintenance fees, and use declarations. Use when checking what's renewing, adding or updating an asset, recording a maintenance filing, or auditing the register for gaps, lapses, and use-in-commerce questions. Receives handoffs from prosecution and clearance work.
launch-review
Full launch review against your framework and risk calibration. Use when the user says "review this launch", "legal review for [feature]", "can we ship this", "what are the legal issues with [product]", or references a launch tracker ticket or PRD that needs a category-by-category review memo.
client-intake
Structured intake — practice-area templates, cross-area issue spotting, conflict flags, and triage classification. Produces a formatted case summary the student analyzes and the professor reviews. Does NOT decide case acceptance. Use when starting a new client intake, running an intake interview, or writing up a new…
gap-surfacer
Reference: shared gap- and comment-tracker framework backing /regulatory-legal:gaps and /regulatory-legal:comments. Tracks open policy gaps with remediation status, ingests gaps from policy-diff, surfaces what's open and aging, routes to owners, and notifies gap owners via Slack with per-send confirmation. Loaded by…