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 yogsoth-ai/stress-test --skill failure-chain-tracinggit clone --depth 1 https://github.com/yogsoth-ai/stress-testWrote 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/yogsoth-ai/stress-test/failure-chain-tracing)<a href="https://agentmods.dev/skills/yogsoth-ai/stress-test/failure-chain-tracing"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/stress-test/failure-chain-tracing/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/yogsoth-ai/stress-test/failure-chain-tracing"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/stress-test/failure-chain-tracing.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.00030 | $0.00476 |
| Opus 5 | $0.00015 | $0.00238 |
| Sonnet 5 | $0.00006 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
failure-chain-tracing 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 9d 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 Chain Tracing Tactic
Trace each failure mode both upstream (root causes) and downstream (cascading effects) to build complete causal chains.
Orchestration
- Start from identified failure mode
- failure-chain-construction traces upstream:
- Why could this mode occur? (immediate cause)
- Why could that cause occur? (root cause)
- Repeat to budget depth (2/4/6 levels)
- failure-chain-construction traces downstream:
- What effect does this mode produce? (local effect)
- What does that effect cause? (system-level effect)
- What is the end impact? (customer/stakeholder effect)
- Chain validated for logical consistency
- Shared causes across multiple modes flagged as systemic risks
Depth Control
- Budget S: 2 levels (immediate cause → mode → local effect)
- Budget M: 4 levels (root cause → ... → system effect)
- Budget L: 6 levels (full chain with environmental factors)
Subagents Dispatched
- failure-chain-construction (upstream and downstream tracing)
- severity-scoring (end-effect severity assessment)
Termination Conditions
- Chain depth exhausted per budget
- Root cause reached (no further upstream cause identifiable)
- End effect reached (stakeholder-level impact identified)
- Circular dependency detected (flag and stop)
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use |
|---|---|
| failure-chain-construction | Build cause-mode-effect chains tracing upstream root causes and downstream cascading effects for each failure mode. |
| severity-scoring | Rate failure mode severity 1-10 based on end-effect impact. Follows AIAG-VDA severity scale calibrated for research artifacts. |
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.
- 9d ago First seen · 64 lines · 30 tokens per session scan A c72f9e27e4a5
failure-chain-tracing is a skill published in the GitHub repository yogsoth-ai/stress-test (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 476 once invoked, about $0.0002 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-31.
Other skills, from other repositories
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
backtest-diagnose
Diagnose failed or underperforming backtests, locate the root cause, and fix the issue.
trace
Use when encountering bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports. Systematic root-cause analysis before any patch — never blind-patches symptoms. Standalone, ends with a final-integration review of the fix. Trigger with /hyperflow:trace, "debug this", "find the root cause", "why…
oma-observability
Intent-based observability + traceability router across layers, boundaries, and signals. Routes to vendor-specific skills via category taxonomy; owns transport tuning, meta-observability, incident forensics. Use for observability, traceability, telemetry, APM, RUM, metrics, logs, traces, profiles, SLO, incident…
oma-debug
Bug diagnosis and fixing specialist - analyzes errors, identifies root causes, provides fixes, and writes regression tests. Use for bug, debug, error, crash, traceback, exception, and regression work.
node-inspect-debugger
Debug Node.js via --inspect + Chrome DevTools Protocol CLI.