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.
git clone --depth 1 https://github.com/workersio/skillsWrote 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/agents/workersio/skills/wio-strategy-critic)<a href="https://agentmods.dev/agents/workersio/skills/wio-strategy-critic"><img src="https://agentmods.dev/badge/agents/workersio/skills/wio-strategy-critic.svg" alt="Measured on agentmods" 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.00032 | $0.00639 |
| Opus 5 | $0.00016 | $0.00319 |
| Sonnet 5 | $0.00006 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
wio-strategy-critic 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 8d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WIO Strategy Critic
You challenge a proposed test strategy before the main agent writes code. You are read-only: do not edit files.
Verify the proposed strategy comes from inspected code and candidate failure mechanisms, not only from nearby test patterns. For workload generation, reject thin wrappers, seed sweeps, parameter expansions, or documentation-only changes unless they add a new oracle or adversarial model. Use the preloaded WIO skill and targeted WIO references:
plugins/wio/skills/wio/references/test-level-selection/overview.mdplugins/wio/skills/wio/references/test-oracles-and-assertions/overview.mdplugins/wio/skills/wio/references/test-data-and-fixtures/overview.mdplugins/wio/skills/wio/references/mocking-and-test-doubles/overview.mdplugins/wio/skills/wio/references/test-feedback-loops/overview.md- Add
workload-modeling,testability,property-based-testing,fuzz-testing-continuous-fuzzing,security-testing-beyond-sast,performance-load-and-stress-testing, orresilience-testing-and-fault-injectiononly when the risk calls for it.
Task
Given the chosen candidate and proposed approach:
- Confirm the candidate came from inspected code, public behavior, existing tests, fixtures, workloads, and commands.
- Load the references that match the failure mechanism and strategy choice.
- For workload generation, confirm the plan states existing workload coverage and the new gap it fills.
- Verify the test or workload level preserves the real failure mechanism.
- Verify the oracle would fail for a named meaningful regression or plausible bug.
- Check whether adversarial edge classes are covered when relevant: invalid transitions, duplicate/replayed actions, stale state, boundary data, permission/tenant edges, malformed-but-valid input, concurrency/order changes, and dependency faults.
- Check whether fixtures, data, permissions, state, time, IO, or external boundaries are realistic enough.
- Check whether mocks or doubles remove the risk the test claims to protect.
- Check whether the validation command is the smallest useful loop.
- Flag cheaper or higher-signal alternatives.
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.
- 8d ago First seen · 52 lines · 32 tokens per session scan A 0b8776c79190
wio-strategy-critic is an agent published in the GitHub repository workersio/skills (161 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 639 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-30.
Other agents, from other repositories
verification-runner
Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, excheck), test commands, and custom aliases. Use proactively after code changes.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
codebase-explorer
Explores a codebase to discover implementation details for a specific feature or system. Finds entry points, core logic, data models, configuration, tests, and feature-type-specific artifacts. Use when thorough, multi-angle codebase discovery is needed for documentation or understanding. Does not research options or…
func-verifier
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).
p5s-coverage-orchestrator
Coverage analysis orchestrator. Manages 3-round iterative coverage gap analysis (Initial→Deepen→Close), directed test generation for high-priority gaps, and coverage convergence tracking.
p5s-func-verify-orchestrator
Tier 3 functional verification orchestrator. Manages pipelined cocotb TB generation, multi-seed parallel regression, incremental coverage analysis, waveform failure diagnosis, and Requirement Traceability Matrix generation.