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 design-fmeagit 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/design-fmea)<a href="https://agentmods.dev/skills/yogsoth-ai/stress-test/design-fmea"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/stress-test/design-fmea/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/design-fmea"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/stress-test/design-fmea.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.00035 | $0.00879 |
| Opus 5 | $0.00017 | $0.00439 |
| Sonnet 5 | $0.00007 | $0.00176 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
design-fmea 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design FMEA Strategy
Systematic failure analysis at the research design level: what functions can fail, how, and with what consequence?
Method
- function-analysis decomposes artifact into function tree
- failure-mode-extraction identifies how each function can fail
- failure-chain-construction builds cause → mode → effect chains
- severity-scoring, occurrence-scoring, detection-scoring rate each mode
- action-priority-matrix classifies priority (H/M/L)
- mitigation-design-sop proposes countermeasures for H-priority items
Budget Table
| Parameter | S | M | L |
|---|---|---|---|
| Functions analyzed | 4 | 10 | 20 |
| Failure modes per function | 2 | 3 | 5 |
| Chain depth (cause levels) | 2 | 4 | 6 |
| Mitigations designed | 3 | 8 | 15 |
Orchestration
function-analysis → failure-mode-extraction → failure-chain-construction
→ [severity-scoring, occurrence-scoring, detection-scoring] (parallel)
→ action-priority-matrix → mitigation-design-sop
→ re-scoring (mitigation-validation tactic)
Subagents
- function-analysis (decompose function tree)
- failure-mode-extraction (identify failure modes)
- failure-chain-construction (cause-mode-effect chains)
- severity-scoring, occurrence-scoring, detection-scoring (S/O/D)
- action-priority-matrix (priority classification)
- mitigation-design-sop (countermeasure design)
Available Tactics
Optional, no fixed order; the final leaf is always a sop.
| Tactic | When to use |
|---|---|
| failure-chain-tracing | Tactic: Trace upstream causes and downstream effects of each failure mode. Builds multi-level cause-mode-effect chains for systemic understanding. |
| mitigation-validation | Tactic: Run mini-FMEA on proposed mitigations to verify they do not introduce new failure modes. Prevents mitigation-induced risks. |
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use |
|---|---|
| action-priority-matrix | Compute Risk Priority Number (RPN = S x O x D), classify failure modes into H/M/L action priority per AIAG-VDA tables. |
| detection-scoring | Rate detectability 1-10 (inverted: 10 = hardest to detect). Estimates how likely current controls would catch the failure before impact. |
| failure-chain-construction | Build cause-mode-effect chains tracing upstream root causes and downstream cascading effects for each failure mode. |
| failure-mode-extraction | Extract structured failure mode list from raw scenarios or artifact analysis. Produces standardized failure mode records. |
| function-analysis | FMEA Step 3: Decompose artifact into function tree — identify what each component is supposed to do before analyzing how it can fail. |
| mitigation-design-sop | Design prevention, detection, and response measures for high-priority failure modes. Produces actionable countermeasure specifications. |
| occurrence-scoring | Rate failure mode occurrence probability 1-10. Estimates how likely each failure mode is to manifest during research execution. |
| 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.
- 12d ago First seen · 91 lines · 35 tokens per session scan A 774a4cbf61ab
design-fmea is a skill published in the GitHub repository yogsoth-ai/stress-test (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 879 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
tournament-judge
Runs a domain-neutral, evidence-based tournament in which independent candidates are reviewed, anonymized, and scored by a blind judge against a rubric fixed before judging. Use when comparing competing plans, designs, implementations, documents, tools, vendors, strategies, or other substantial options; when the user…
sector-rotation
An analysis framework for comparing industries in the Chinese A-share stock market, using business conditions, price momentum, valuation, and money flows. It produces rankings and higher- or lower-allocation suggestions.
browser_cdp
A health check for Python code that produces a score, letter grade, and measures of issues such as complexity, duplication, dead code, dependencies, and architecture.
shogun-screenshot
A screenshot tool for getting images from a computer or web page and then cropping, resizing, or masking sensitive information. Playwright is a browser-automation tool used here to capture web pages.
creating-skills
Guide for creating Claude Code skills following Anthropic's official best practices. Use when user wants to create a new skill, build a skill, write SKILL.md, update an existing skill, or needs skill creation guidelines. Provides structure, frontmatter fields, naming conventions, and new features like dynamic context…
config-validator
Validate AIWG configuration files and project setup for correctness and completeness.