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 mitigation-designgit 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/mitigation-design)<a href="https://agentmods.dev/skills/yogsoth-ai/stress-test/mitigation-design"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/stress-test/mitigation-design/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/mitigation-design"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/stress-test/mitigation-design.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.00033 | $0.00600 |
| Opus 5.5 | $0.00013 | $0.00240 |
| Sonnet 5.5 | $0.00007 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
mitigation-design 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 1mo 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mitigation Design Strategy
Design countermeasures for high-priority failure modes across three layers: prevention, detection, response.
Method
- mitigation-design-sop generates countermeasures for each H-priority failure:
- Prevention: eliminate or reduce occurrence
- Detection: improve ability to detect before impact
- Response: contingency plan if failure occurs
- re-scoring re-evaluates S/O/D with mitigations in place
- mitigation-validation runs mini-FMEA on mitigations themselves
- Iterate until all H-priority items reach M or L after mitigation
Budget Table
| Parameter | S | M | L |
|---|---|---|---|
| Mitigations per failure mode | 1 | 2 | 3 |
| Re-scoring rounds | 1 | 2 | 3 |
| Mitigation validation depth | shallow | standard | full FMEA |
Orchestration
[H-priority failures] → mitigation-design-sop
→ re-scoring → action-priority-matrix (re-classify)
→ [still H?] → mitigation-validation → iterate
→ [M or L?] → accept, document residual risk
Subagents
- mitigation-design-sop (countermeasure generation)
- re-scoring (post-mitigation S/O/D)
- action-priority-matrix (re-classification)
Available Tactics
Optional, no fixed order; the final leaf is always a sop.
| Tactic | When to use |
|---|---|
| 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. |
| mitigation-design-sop | Design prevention, detection, and response measures for high-priority failure modes. Produces actionable countermeasure specifications. |
| re-scoring | Re-evaluate S/O/D scores after mitigation measures are in place. Validates that mitigations actually reduce risk as expected. |
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.
- 1mo ago First seen · 75 lines · 33 tokens per session scan A ed7e74fda4e8
mitigation-design is a skill published in the GitHub repository yogsoth-ai/stress-test (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 600 once invoked, about $0.0001 per session on Opus 5.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.
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.
oma-observability
Design or troubleshoot telemetry, SLOs, and incident diagnostics. Route to the relevant signal, system boundary, or vendor guide.
node-inspect-debugger
Debug Node.js via --inspect + Chrome DevTools Protocol CLI.
oma-debug
Diagnose a reproducible failure, fix its cause, and verify the regression. Use for crashes, incorrect behavior, and failing tests.
aiwg-doctor
Run a comprehensive health check on the AIWG installation and workspace with pass/fail diagnostics and remediation steps.