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 weakness-classificationgit 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/weakness-classification)<a href="https://agentmods.dev/skills/yogsoth-ai/stress-test/weakness-classification"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/stress-test/weakness-classification/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/weakness-classification"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/stress-test/weakness-classification.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.00397 |
| Opus 5.5 | $0.00012 | $0.00159 |
| Sonnet 5.5 | $0.00006 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
weakness-classification 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.
What it actually says
Weakness Classification
Classifies discovered weaknesses into severity tiers.
Execution
Subagent — spawned via subagent-spawning/spawn-agent.
Why Subagent
Classification requires careful reasoning about impact scope and exploitability — dedicated context prevents bias from the discovery process.
Input
- raw_finding: The weakness finding with context from discovery
- artifact_context: The original artifact being validated
Output
- severity:
fatal|major|minor|cosmetic - category: type of weakness (logical, evidential, methodological, scope, assumption, implementation)
- justification: why this severity level
- exploitability: how easily this weakness could be exploited/triggered in practice
Classification Scheme
- fatal: Invalidates the core claim — artifact cannot be used as-is
- major: Significantly undermines validity but not fatal — requires substantial revision
- minor: Weakens periphery — addressable without fundamental changes
- cosmetic: Presentation/clarity issue only — does not affect validity
Budget
One unit = one classification. Called per finding.
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use |
|---|---|
| spawn-agent | Spawn a customized CC subagent with full MCP tool access. Used by SOPs that declare execution: subagent. |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 59 lines · 30 tokens per session scan A 46606b48be92
weakness-classification is a skill published in the GitHub repository yogsoth-ai/stress-test (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 397 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.