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 slate-draftgit 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/slate-draft)<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/slate-draft"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/slate-draft/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/slate-draft"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/slate-draft.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.00160 | $0.02211 |
| Opus 5.5 | $0.00064 | $0.00884 |
| Sonnet 5.5 | $0.00032 | $0.00442 |
| Haiku 4.5 | $0.00016 | $0.00221 |
Grade A, and why
slate-draft 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 yesterday.
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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slate Draft
Purpose
Create the terminal draft: a staffing recommendation record for partner approval, populated only from governed.json.
When to use
After constraint-check, when the user asks for a slate, recommendation, partner approval note or staffing summary.
When NOT to Use
- Client-facing emails, kickoff thank-you notes or other correspondence.
- Scoring or ranking candidates — use fit-score instead.
- Deciding eligibility — use constraint-check instead.
Inputs
roles.json + bench.json + constraints.json + governed.json using contract ps.engagement-staffing-bench-match.v1. All four are required: the validator re-derives governed.json from the upstream inputs and refuses with no output if it differs (#9.8). It writes validated.json (--out) and the rendered draft slate-draft.md (--draft-out, required) together: both files or neither.
Steps
- Run the secondary validator. Draft only from
validated.json. If the validator exits non-zero, printserror:or the input is malformed, stop and report the one-line error; never hand-build the slate. The draft is the engine-renderedslate-draft.md: present it verbatim. You may add prose only outside the tables, and never change a figure, verdict or ID; steps 2-6 describe what it already contains. - Lead with any Govern refusals, especially if the top provisional candidate was disqualified.
- For each role, list final eligible candidates in engine order with fit score, component highlights, availability, utilisation after staffing, rate-band context and citations (record IDs and rule sections only). Check
constraints_considered[]before placing anyone in the recommendation. - Include ineligible and needs-review candidates in a separate "not recommended" section with conflict category, blocking rule and citation. Label eligible candidates below 70.0 as
below_score_floorunderfit-scoring-rubric.md #7.2. If any applicable conflict record is unexplained, unknown or not clearly resolved, move the candidate to Needs Review even if another upstream field says eligible. - Write the gap statement verbatim for any role with no eligible candidate above the recommendable score floor.
- Start the output with the exact lines
DRAFT - HUMAN REVIEW REQUIREDandDRAFT - pending partner approval and independence/resource-management review, and present it to the user for review.
What ships with it
10 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.
- contracts/ps.engagement-staffing-bench-match.v1.json 15 KB
- references/fit-scoring-rubric.md 4.0 KB
- references/independence-eligibility-rules.md 13 KB
- scripts/constraint_check.py 101 KB runs code
- scripts/fit_score.py 29 KB runs code
- scripts/input_guard.py 13 KB runs code
- scripts/safety_text.py 27 KB runs code
- scripts/slate_rank.py 4.6 KB runs code
- scripts/slate_validate.py 69 KB runs code
- scripts/steering_guard.py 187 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.
- yesterday First seen · 77 lines · 160 tokens per session scan A bef536845159
slate-draft is a skill published in the GitHub repository microsoft/cat-agent-skills (101 stars, last pushed yesterday), licensed MIT. It adds 160 tokens to every session and 2,211 once invoked, about $0.0006 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-11-07.
slate-draft compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| slate-draftmicrosoft/cat-agent-skills | Skill | 101 | yesterday | MIT | A | 160 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | yesterday | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 100k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 4d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |