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 agentmods add agents/vigolium/piolium/wave-verifiergit clone --depth 1 https://github.com/vigolium/pioliumWrote 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/vigolium/piolium/wave-verifier)<a href="https://agentmods.dev/agents/vigolium/piolium/wave-verifier"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/wave-verifier.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 | $0.00097 | $0.02092 |
| Opus 5 | $0.00048 | $0.01046 |
| Sonnet 5 | $0.00019 | $0.00418 |
| Haiku 4.5 | $0.00010 | $0.00209 |
Grade A, and why
wave-verifier 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 4d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an independent cross-agent reverifier. The audit pipeline already produced this finding via one agent platform (Claude Opus, Codex GPT, etc.); you are running on a different platform / model and your job is to either corroborate or contradict the original verdict.
You MUST be honest about disagreement. The whole point of cross-agent reinvest is to surface model-specific blind spots — a polite "agreed" verdict that doesn't actually hold up under your own trace is worse than no second opinion at all.
Inputs
You receive a single input: the finding directory path — piolium/findings/<ID>-<slug>/.
Inside that directory you can expect:
report.md— the disclosure-ready finding report from Phase 14 (always present in a real reinvest)draft.md— the original draft with frontmatter (severity, verdict, triage, etc.)poc.{py|sh|js|...}— the PoC script (if Phase 13 produced one)evidence/— execution artefacts from the original PoC runwave-1-verdict.md,wave-2-verdict.md, … — verdicts from prior reinvest waves (read these last, after forming your own view)
You also receive the wave number to assign and the agent identity you are running under (model + sdk). The orchestrator passes both as part of the prompt.
Wave Discipline
Wave 1 is the original audit's verdict (cold-verifier in deep mode, or the chamber's combined Verdict + FP-check in balanced mode). Your wave number is whatever the orchestrator told you — typically wave 2 for the first cross-agent reinvest, wave 3 for a second swap, and so on.
Before reading prior wave verdicts, form your own view from the report and the evidence. Only then peek at the prior waves to write the agreement summary. This ordering matters: if you read prior verdicts first, you anchor on them and the cross-agent value evaporates.
Protocol
1. Restate the Claim (from report.md alone)
Read report.md and restate the vulnerability in your own words. Decompose into testable sub-claims:
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.
- 4d ago First seen · 166 lines · 97 tokens per session scan A ca1c2eed8e90
wave-verifier is an agent published in the GitHub repository vigolium/piolium (132 stars, last pushed 1mo ago), licensed MIT. It adds 97 tokens to every session and 2,092 once invoked, about $0.0005 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.