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 history-retrievegit 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/history-retrieve)<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/history-retrieve"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/history-retrieve/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/history-retrieve"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/history-retrieve.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.00085 | $0.00555 |
| Opus 5.5 | $0.00034 | $0.00222 |
| Sonnet 5.5 | $0.00017 | $0.00111 |
| Haiku 4.5 | $0.00009 | $0.00056 |
Grade A, and why
history-retrieve 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
History Retrieve
Purpose
Enrich the fault payload with grounded history: the asset's prior work orders (with their recorded failure modes and dates), similar failures on like assets, PM compliance, and the OEM manual / troubleshooting-guide sections that describe the candidate failure modes.
When to use
- After fault-intake, in every triage run.
- "Has failed like this before?" / "pull the work-order history" / "find the manual section".
Inputs
fault-intake.json(contract inputs from fault-intake).- Work-order history export (CSV): date, asset, failure_mode, action, downtime.
- OEM manual excerpt (PDF) and troubleshooting guide (Markdown).
- Optional: historian sample (CSV) — vibration/temperature trend. History input is optional; the plugin runs from documents alone.
Steps
- Filter the work-order history to this
asset_id; extract each prior WO as{failure_mode, days_ago, action}intohistory.prior_work_orders[]. - Set
history.window_daysto the span covered and count repeat symptomatic fixes. - Locate the OEM manual / troubleshooting sections matching the reported symptoms; carry
their citations forward (they become the
citationon ranked causes). - Write the enriched
history{}block back onto the contract payload.
Output
The contract payload with a populated history{} object and manual/guide citations — the
input to failure-mode-rank.
Grounding requirements
Every prior work order cites its CMMS record ID; every manual reference cites the manual section (e.g. "OEM Pump Manual CP-200 §6.3").
Constraints
- Retrieval only — do not diagnose or rank here (engine/LLM split).
- Do not infer a failure mode for a prior WO that its record does not state.
- Historian data is optional context, never a required input.
Escalation / uncertainty
- If history is unavailable, proceed on documents alone and note it in
escalations[]; do not block the run.
What ships with it
6 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 · 53 lines · 85 tokens per session scan A ef6bcf12557a
history-retrieve is a skill published in the GitHub repository microsoft/cat-agent-skills (93 stars, last pushed today), licensed MIT. It adds 85 tokens to every session and 555 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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…