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 commands/samibs/skillfoundry/failure-analysisgit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/commands/samibs/skillfoundry/failure-analysis)<a href="https://agentmods.dev/commands/samibs/skillfoundry/failure-analysis"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/failure-analysis.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00385 |
| Opus 5 | $0.00000 | $0.00192 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00038 |
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 yesterday.
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.
- yesterday First seen · 61 lines · 0 tokens per session scan A 7f74ffe4bc2e
failure-analysis is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 385 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.