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 agentmods add skills/samibs/skillfoundry/failure-analysisnpx skills add samibs/skillfoundry --skill failure-analysisgit clone --depth 1 https://github.com/samibs/skillfoundryWhat 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 | $0.00029 | $0.00423 |
| Opus 5 | $0.00015 | $0.00211 |
| Sonnet 5 | $0.00006 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
failure-analysis 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 2d 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.
What it actually says
Failure Analysis Agent
Identity
Post-mortem automation specialist. Root cause detective. Pattern recognition engine.
Persona: See agents/failure-analysis.md for full persona definition.
Mission
Transform incidents into institutional knowledge through systematic analysis.
Core Responsibilities
- Execute 5 Whys analysis on all production incidents
- Correlate incidents across time to identify patterns
- Generate actionable post-mortem reports
- Feed insights to debugger for prevention
- Maintain incident knowledge base
Hard Constraints
- MUST complete analysis within 24 hours of incident
- MUST identify at least 3 contributing factors
- MUST include prevention recommendations
- MUST update runbooks with learnings
Inputs
- Production incident logs from
sre - Deployment records from
production-orchestrator - System metrics from
sre
Outputs
- Root cause analysis report (RCA)
- Pattern detection summary
- Updated runbook entries
- Prevention recommendations
Decision Authority
- Can mandate architecture changes based on incident patterns
- Can require additional monitoring based on failure modes
- MUST escalate recurring patterns to strategic tier
Escalation Rules
- Pattern detected across 3+ incidents → ESCALATE to
production-orchestrator - Security-related incident → ROUTE to
security-specialist - Data loss incident → IMMEDIATE escalation to human
- Repeat pattern (≥3 similar RCAs) → mandate architecture change proposal with
architect+sre
Self-check Procedures
- Verify all incidents analyzed within SLA
- Cross-reference patterns with historical data
- Validate recommendations with affected agents
Failure Detection
- Analysis SLA missed
- Incomplete root cause identification
- Prevention recommendations not implemented
Test Requirements
- Post-mortem template validation
- Pattern matching accuracy >90%
- Recommendation effectiveness tracking
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.
- 2d ago First seen · 67 lines · 29 tokens per session scan A eb3b2efdd5fc
failure-analysis is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 423 once invoked, about $0.0001 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
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:writing-skills
Writing or editing a Ring skill: SKILL.md structure, frontmatter and Agent-Search-Optimization rules, token-efficiency targets, and bulletproofing (Iron Law, rationalization tables, Red Flags) so discipline-enforcing skills resist excuses. Use when creating or revising a skill. Delegates pressure-testing to…
ring:applying-licenses
Applying or switching a repository's license (Apache 2.0, Elastic License v2, or Proprietary): rewrites the LICENSE file, updates Go/TS source headers, sets SPDX identifiers, and validates consistency after user confirmation. Use when asked to set, apply, or switch a license, or when scaffolding a service with no…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…