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 fault-intakegit 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/fault-intake)<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/fault-intake"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/fault-intake/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/fault-intake"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/fault-intake.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.00077 | $0.00613 |
| Opus 5.5 | $0.00031 | $0.00245 |
| Sonnet 5.5 | $0.00015 | $0.00123 |
| Haiku 4.5 | $0.00008 | $0.00061 |
Grade A, and why
fault-intake 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fault Intake
Purpose
Turn the raw breakdown inputs (technician fault note, operator report, alarm/event log, asset tag) into structured contract inputs: a normalized symptom list, alarm codes, the asset identity, and its criticality/downtime attributes.
When to use
- "Triage fault on " / "work this breakdown" / "what's wrong with ?"
- "Read the fault note / alarm log for ."
- Start of any Maintenance Triage run.
Inputs
- Fault note / operator report (TXT, email, or extract): free-text symptoms.
- Alarm / event log (CSV): timestamped alarm codes for the asset.
- Asset register + criticality (XLSX / CSV): class (A/B/C), downtime cost/hr, redundancy.
- Emits inputs for contract
mfg.maintenance-triage.v1.
Steps
- Confirm the asset tag resolves in the asset register; carry its criticality class,
downtime_cost_per_hr, andredundancyonto the contract. - Map free-text symptoms to the controlled vocabulary in
references/failure-mode-library.md#1 (e.g. "runs hot and trips" ->overload_trip,motor_hot). Never invent a symptom that is not evidenced. - Extract alarm codes from the event log as
alarm_codes[]. - Produce
fault-intake.jsonwithcontract_version,asset_id,asset_criticality,downtime_cost_per_hr,symptoms[],alarm_codes[], and an emptyhistory{}.
Output
fault-intake.json conforming to the contract inputs — the entry payload of the flow.
Grounding requirements
Every symptom cites the source line (fault note or alarm log). Asset attributes cite the asset register row.
Constraints
- Symptom vocabulary is fixed by
references/failure-mode-library.md#1 — map, do not guess. - Do not rank causes or set priority here — that is the Analyze skills' job (engine/LLM split).
- Never fabricate an asset attribute; a missing tag or criticality is an escalation.
Escalation / uncertainty
- Asset tag not found, criticality class missing, or symptoms un-mappable: stop and ask the
technician; record it in the contract
escalations[].
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 · 54 lines · 77 tokens per session scan A 311e2999069a
fault-intake is a skill published in the GitHub repository microsoft/cat-agent-skills (93 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 613 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.