failure-mode-rank

failure-mode-rank is a skill for Claude Code, Codex from microsoft/cat-agent-skills. It costs 71 tokens per session (524 once invoked), scanned A, original, MIT.

A fault-analysis step that ranks possible equipment failure modes by comparing symptoms and alarm codes with a failure library and previous failures. A failure mode is a specific way equipment can fail.

In plain words
What is it for?
It helps investigate breakdowns, compare likely causes, and identify recommended fixes with references to the equipment manual or failure library.
Why use it?
It gives maintenance staff a consistent list of likely causes instead of relying only on an individual diagnosis. Repeated failures can be promoted as possible underlying causes rather than treated as one-off symptoms.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one.

Good fit It helps investigate breakdowns, compare likely causes, and identify recommended fixes with references to the equipment manual or failure library.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/cat-agent-skills/failure-mode-rank
About the project

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.

microsoft/cat-agent-skills · 93 stars · on GitHub

Install

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.

Any agent
npx skills add microsoft/cat-agent-skills --skill failure-mode-rank
Clone the repo
git clone --depth 1 https://github.com/microsoft/cat-agent-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for failure-mode-rank

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/failure-mode-rank/github.svg)](https://agentmods.dev/skills/microsoft/cat-agent-skills/failure-mode-rank)
Your own site
<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/failure-mode-rank"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/failure-mode-rank/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.

agentmods 80×15 button for failure-mode-rank

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/failure-mode-rank"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/failure-mode-rank.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 524 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00071 $0.00524
Opus 5.5 $0.00028 $0.00210
Sonnet 5.5 $0.00014 $0.00105
Haiku 4.5 $0.00007 $0.00052

Measured today against content hash 9455c09c9c53, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

failure-mode-rank 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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/fault_rank.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

submissions/maintenance-triage/skills/failure-mode-rank/SKILL.md · 50 lines

What it actually says

Failure-Mode Rank

Purpose

Deterministically rank the candidate failure modes for the fault, matching symptoms and alarm codes to the failure-mode library and applying the repeat-failure root-cause promotion rule.

When to use

  • After history-retrieve, in every triage run.
  • "What's the likely cause?" / "rank the failure modes" / "is the reset masking something?".

Inputs

  • The contract payload with symptoms[], alarm_codes[], and history{} (contract mfg.maintenance-triage.v1).

Steps

  1. Validate the payload against the contract.
  2. Run scripts/fault_rank.py --intake fault-intake.json --out ranked-causes.json.
  3. Do not restate or recompute any score in prose; quote the engine output verbatim.
  4. Emit the {ranked_causes} contract payload.

Output

Contract mfg.maintenance-triage.v1 with populated ranked_causes[] (rank, failure_mode, match_score, evidence, recommended_fix, confidence, source=engine:fault_rank, citation) and history.repeat_promotion — the {ranked_causes} hop.

Grounding requirements

Every ranked cause carries its OEM manual / library citation; the promotion of a root cause over a symptomatic fix cites references/failure-mode-library.md #3.1.

Constraints

  • All ranking math happens in the engine. The model must never re-rank causes itself.
  • No priority or cost talk here — that is criticality-rank's job.
  • Never suppress the repeat-failure promotion because a cheaper symptomatic fix "usually works".

Escalation / uncertainty

  • Top candidate confidence below the 0.75 floor, or two candidates within the ambiguity band: the engine adds to escalations[]; surface it and route to a human diagnosis (failure-mode-library.md #4.1-#4.2).
Files

What ships with it

7 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.

Changes

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.

  1. today First seen · 50 lines · 71 tokens per session scan A 9455c09c9c53

Subscribe to this mod's changes

failure-mode-rank is a skill published in the GitHub repository microsoft/cat-agent-skills (93 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 524 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.

Related

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…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

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.

open-metadata/OpenMetadata · 37 tokens

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…

zebbern/claude-code-guide · 71 tokens

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…

adobe/skills · 112 tokens

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.

rmyndharis/antigravity-skills · 36 tokens

ci-fixer

CI failures - read error, minimal fix, verify.

sipyourdrink-ltd/bernstein · 15 tokens