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 power-automate-documentationgit 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/power-automate-documentation)<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/power-automate-documentation"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/power-automate-documentation/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/power-automate-documentation"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/power-automate-documentation.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.00072 | $0.03521 |
| Opus 5.5 | $0.00029 | $0.01408 |
| Sonnet 5.5 | $0.00014 | $0.00704 |
| Haiku 4.5 | $0.00007 | $0.00352 |
Grade A, and why
power-automate-documentation 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 1mo 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are producing a technical reference document for a Power Automate solution export: what each flow does, in plain English, and every place it reaches outside itself to read, write, or delete data. The source of truth is always the JSON inside the solution zip, never the flow's display name or your assumptions about what a flow "probably" does.
Inventory before you narrate. The failure mode to avoid: skimming a flow's JSON, writing a plausible-sounding summary, and closing with a note that "a fuller audit would require deeper parsing." If you ever find yourself about to write a sentence like that, it means you skipped the inventory step below — go back and do it, don't disclose the shortcut instead of taking it. Every action in every flow gets listed and accounted for; there is no partial-credit version of this task.
Solution Zip Anatomy
An unpacked solution zip has this shape:
solution.xml—SolutionManifest:UniqueName,Version,Managed(0 = unmanaged, 1 = managed),Publisher.customizations.xml— a<Workflows>element listing every flow in the solution, and a<connectionreferences>element.WorkflowIdandNameare always attributes on<Workflow>; everything else (JsonFileName,Category,StateCode,StatusCode, ...) appears as attributes in compact/hand-built exports but as child elements in full Dataverse exports (e.g. viapac solution unpackor a live environment export) — read whichever form is present. WhenStateCode/StatusCodeare present,0/1means the flow is Draft (off) and1/2means it's Activated (on) — worth a one-line note per flow.<connectionreferences>is often empty even when flows use connectors — the connection is then resolved through the flow JSON itself (see below). Real Dataverse exports may instead ship one file per connection reference under a top-levelconnectionreferences/folder — check for that folder too, and treat it as the same information as an inline<connectionreferences>entry.Workflows/*.json— one file per flow, keyed atproperties.definition.triggersandproperties.definition.actions, using the standard Logic Apps workflow-definition schema. Full exports also carryproperties.connectionReferences— see below.
If more than one solution zip is provided in the same request, treat each as an independent solution for the per-flow steps below, but pool their flow-ID maps before resolving child-flow calls, so a call in one zip can resolve to a flow shipped in another.
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.
- 1mo ago First seen · 158 lines · 72 tokens per session scan A 61734a905c94
power-automate-documentation is a skill published in the GitHub repository microsoft/cat-agent-skills (93 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 3,521 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-09-03.
Other skills, from other repositories
ocr-pipeline-and-quality
Xberg OCR backends, preprocessing, caching, page acceptance, hOCR, tables, cross-backend quality. Use for OCR behavior or A/B quality work.
pdf-backends
Xberg PDF extraction: native/Pdfium backend selection, rendering, encryption, OCR fallback, capability gaps. Use for PDF engine work.
add-sharepoint
Adds SharePoint Online connector to a Power Apps code app. Use when reading lists, managing documents, or integrating with SharePoint sites. Can also create new SharePoint lists.
excel2json
An Excel conversion tool that turns worksheet data into JSON, a structured text format commonly used by programs and web APIs. It supports row-based, column-based, and two-dimensional output, and converts dates to a standard text form.
rag-web-fallback
Only reach for external web search when the local corpus comes back empty or clearly insufficient. Forces the agent to try knowledge-rag first, then explicitly document why it needed to escalate. Prevents wasted API cost, latency, and (in air-gapped deployments) accidental network calls.
hermes3000-writing
Use Hermes3000 to plan, draft, revise, save, check consistency, and export long-form manuscripts through the Hermes3000 AI writing portal API. Use for novels, fiction series, nonfiction books, whitepapers, long reads, chapter outlines, character/world-building, style guides, consistency memory, and DOCX/PDF/EPUB/HTML…