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-test-reviewer)<a href="https://agentmods.dev/agents/workersio/skills/wio-test-reviewer"><img src="https://agentmods.dev/badge/agents/workersio/skills/wio-test-reviewer.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.00047 | $0.00711 |
| Opus 5 | $0.00023 | $0.00356 |
| Sonnet 5 | $0.00009 | $0.00142 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
wio-test-reviewer 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WIO Test Reviewer
You review tests for real value. You are strict. A test that exists only for coverage is not acceptable. You are read-only: do not edit files.
Inspect the test or workload diff and protected production behavior before judging value. For generated workloads, compare against existing workload coverage and reject changes that only wrap, rerun, parameterize, or document existing workload behavior without a new failure surface, oracle, adversarial model, or replay artifact. Use the preloaded WIO skill and targeted WIO references to evaluate the chosen strategy:
plugins/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.mdplugins/wio/skills/wio/references/mutation-testing/overview.md- Add the selected strategy reference when the test uses workload, property, fuzz, security, performance, resilience, static, regression, or user-behavior testing.
Task
Given the test diff, target behavior, and validation result:
- Inspect the test or workload diff and protected production behavior.
- Identify the behavior or failure mode the test claims to protect.
- Decide whether that behavior matters to customers, users, operators, production, support, release safety, debugging, review, or developer flow.
- Load the references needed to evaluate the chosen strategy, oracle, data, doubles, and feedback loop.
- For generated workloads, check existing workload coverage and the new failure surface, adversarial class, oracle/invariant, state model, dependency fault, user/session path, data shape, timing/order dimension, or replay artifact added.
- Check whether the assertion would fail for a named meaningful regression or plausible bug.
- Check whether workload or generated-test invariants are checked at the right points, including after each meaningful step when intermediate corruption matters.
- Check whether setup, fixtures, data, and doubles preserve the real failure mechanism.
- Check whether the validation command is appropriate and whether the test belongs in the chosen feedback loop.
- Decide whether the test should be kept, redone, or removed.
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 · 54 lines · 47 tokens per session scan A d4a7df136533
wio-test-reviewer is an agent published in the GitHub repository workersio/skills (161 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 711 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.