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 copilot-studio-topic-blueprintgit 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/copilot-studio-topic-blueprint)<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/copilot-studio-topic-blueprint"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/copilot-studio-topic-blueprint/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/copilot-studio-topic-blueprint"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/copilot-studio-topic-blueprint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00125 | $0.00866 |
| Opus 5 | $0.00063 | $0.00433 |
| Sonnet 5 | $0.00025 | $0.00173 |
| Haiku 4.5 | $0.00013 | $0.00087 |
Grade A, and why
copilot-studio-topic-blueprint 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 9d ago.
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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Turn a one or two sentence use case into a build-ready Microsoft Copilot Studio agent blueprint the maker can implement directly. You design and specify; you do not build in the maker's tenant.
Instructions
-
Capture the use case. If the user gave a one-line description, use it. If the request is vague (no clear user, task, or data source), ask one focused question to fill the biggest gap, then proceed. Do not stall on missing detail you can reasonably assume; state your assumptions instead.
-
Produce the blueprint in exactly these eight sections, in order:
- Recommendation. State the agent type (declarative, custom, or custom engine) and the orchestration mode (generative or classic), each with a one-line reason. Default to a custom Copilot Studio agent with generative orchestration unless the use case clearly needs otherwise.
- Topics. List 3 to 7 topics. For each: a name, a one-line generative-orchestration description that names the task and includes a "use when" clause, and the key nodes in order (Question, Condition, Message, Call an action, and so on). Note any input the topic must collect.
- Tools and actions. List the tools, connectors, or Power Automate flows the agent needs. For each: a name, a description written for orchestrator selection, typed inputs and outputs, and the failure path.
- Knowledge. List the knowledge sources to attach and the scope of each. Note when knowledge should answer versus when a topic or tool should.
- Variables. List the global variables the agent needs, with type and purpose.
- Welcome experience. Provide valid Adaptive Card JSON for conversation start: a short greeting plus 3 starter prompts drawn from the topics above.
- Security and cost. State the authentication mode (None, Microsoft Entra, or generic OAuth 2.0) and why, any DLP considerations, and the main Copilot Credits cost drivers with one tip to control them. Use Copilot Credits terminology, not "messages".
- First test plan. Give 5 test utterances and the expected topic or tool each should trigger, to run in the free embedded test chat.
-
Keep it build-ready. Every element must be specific enough to implement without further design work. Prefer concrete names, typed signatures, and ordered node lists over prose.
What ships with it
2 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.
- 9d ago First seen · 69 lines · 125 tokens per session scan A dff01ef0faf7
copilot-studio-topic-blueprint is a skill published in the GitHub repository microsoft/cat-agent-skills (66 stars, last pushed yesterday), licensed MIT. It adds 125 tokens to every session and 866 once invoked, about $0.0006 per session on Opus 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…