process-fmea

process-fmea is a skill for Claude Code, Codex from yogsoth-ai/stress-test. It costs 29 tokens per session (870 once invoked), scanned A, original, Apache-2.0.

A risk-analysis strategy for finding how a research process can fail while it is being carried out. FMEA, or failure mode and effects analysis, lists failures, traces their consequences, scores their risk, and designs controls.

In plain words
What is it for?
Use it to map research steps, identify process failure modes, prioritize them, and define measures to reduce or detect them.
Why use it?
It separates problems in execution—such as data-collection errors or changes in method—from flaws in the original research design.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit Use it to map research steps, identify process failure modes, prioritize them, and define measures to reduce or detect them.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yogsoth-ai/stress-test/process-fmea
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 yogsoth-ai/stress-test --skill process-fmea
Clone the repo
git clone --depth 1 https://github.com/yogsoth-ai/stress-test

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 process-fmea

README.md
[![agentmods](https://agentmods.dev/badge/skills/yogsoth-ai/stress-test/process-fmea/github.svg)](https://agentmods.dev/skills/yogsoth-ai/stress-test/process-fmea)
Your own site
<a href="https://agentmods.dev/skills/yogsoth-ai/stress-test/process-fmea"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/stress-test/process-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.

agentmods 80×15 button for process-fmea

Your own site · 80×15
<a href="https://agentmods.dev/skills/yogsoth-ai/stress-test/process-fmea"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/stress-test/process-fmea.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 870 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.00029 $0.00870
Opus 5 $0.00015 $0.00435
Sonnet 5 $0.00006 $0.00174
Haiku 4.5 $0.00003 $0.00087

Measured 7d ago against content hash 57ab21a53cbb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

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

skills/process-fmea/SKILL.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Process FMEA Strategy

Analyzes failure modes in the research execution process — not what the design gets wrong, but what can go wrong during implementation.

Method

  1. function-analysis maps the execution process steps
  2. failure-mode-extraction identifies process-level failure modes (data collection errors, methodology drift, resource constraints)
  3. failure-chain-construction traces process failures to outcome impacts
  4. severity-scoring, occurrence-scoring, detection-scoring rate each mode
  5. action-priority-matrix classifies priority
  6. mitigation-design-sop designs process controls

Budget Table

Parameter S M L
Process steps analyzed 4 10 20
Failure modes per step 2 3 4
Chain depth 2 3 5
Process controls designed 2 6 12

Orchestration

function-analysis (process mode) → failure-mode-extraction
  → failure-chain-construction
  → [severity-scoring, occurrence-scoring, detection-scoring] (parallel)
  → action-priority-matrix → mitigation-design-sop
  → re-scoring

Subagents

  • function-analysis (process step mapping)
  • failure-mode-extraction (process failure identification)
  • failure-chain-construction (process-to-outcome chains)
  • severity-scoring, occurrence-scoring, detection-scoring (S/O/D)
  • action-priority-matrix (priority classification)
  • mitigation-design-sop (process control 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.

Read the full file on GitHub · 92 lines

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. 7d ago First seen · 92 lines · 29 tokens per session scan A 57ab21a53cbb

Subscribe to this mod's changes

process-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 29 tokens to every session and 870 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-09-03.

Related

Other skills, from other repositories

relax-dev-debug

Develop and debug the Relax reinforcement learning project. Use this skill whenever modifying code in the relax/ directory, or running remote training jobs on a Ray cluster for validation. Also use it when the user mentions training, debugging training runs, submitting Ray jobs, or fixing training errors.

redai-infra/Relax · 60 tokens

research-ideation

Quant-focused research ideation pipeline: scope selection (3 stages) → anchor-first literature grounding → single-core idea generation → iterative refinement → ELO tournament ranking (Final = N+R+C−D) → update evo-memory → user selects direction → expand into manuscript-quality proposal. Optimized for incremental…

CamusGIT/EvoQuant · 151 tokens

quant-experiment-runtime

Quant research experiment executor: discover an offline source database under the workdir's code-repo, build a panel, run a Research Artifact's entry point to compute research-object values, and evaluate IC/ICIR/RANKIC/coverage metrics. Runtime = Experiment Executor; it runs a Research Artifact via a Python-native…

CamusGIT/EvoQuant · 179 tokens

local-paper-navigator

Find and read papers from the local papers library (repo papers/, mounted at /papers/). Three native tools form a reading funnel: papersearch (one line per paper), paperread (card + section outline), papersection (one verbatim section — the only full-text access). Use when: find papers in the local library, read a…

CamusGIT/EvoQuant · 119 tokens

experiment-pipeline

Guides structured 4-stage experiment execution with attempt budgets and gate conditions: Stage 1 initial implementation (reproduce baseline), Stage 2 hyperparameter tuning, Stage 3 proposed method validation, Stage 4 ablation study. Integrates with evo-memory (load prior strategies, trigger IVE/ESE) and…

CamusGIT/EvoQuant · 129 tokens

paper-review

Guides self-review of YOUR OWN academic paper before submission with adversarial stress-testing. Core method: 5-aspect checklist (contribution sufficiency, writing clarity, results quality, testing completeness, method design), counterintuitive protocol (reject-first simulation, delete unsupported claims, score trust…

CamusGIT/EvoQuant · 152 tokens