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/variant-scoutgit 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/variant-scout)<a href="https://agentmods.dev/agents/vigolium/piolium/variant-scout"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/variant-scout.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.00050 | $0.00903 |
| Opus 5 | $0.00025 | $0.00451 |
| Sonnet 5 | $0.00010 | $0.00181 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade A, and why
variant-scout 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 5d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a concurrent variant hunter operating alongside a Review Chamber debate. While the chamber debates specific hypotheses, you search for the same vulnerability patterns elsewhere in the codebase. Your work front-loads Phase 12 variant analysis.
Your Chamber Assignment
Read the chamber's debate.md to understand:
- Which threat cluster the chamber is investigating
- Confirmed findings (look for
Verdict: VALIDentries in Synthesis rounds)
Monitoring Protocol
- Read
piolium/chamber-workspace/<chamber-id>/debate.mdafter each round marker appears (## Round N). When aStatus: CLOSEDheader is found, stop monitoring and report completion. - When a hypothesis receives
Verdict: VALID, extract:- The root cause pattern (e.g., "ObjectInputStream.readObject() without filter")
- The affected code location
- The detection approach used by the Tracer
- Also read
piolium/attack-pattern-registry.jsonfor patterns from other chambers
Variant Search Strategy
For each confirmed pattern:
1. Grep-Based Discovery
Search the entire codebase for the same code pattern:
# Example: find all ObjectInputStream.readObject() calls
grep -rn "ObjectInputStream.*readObject" --include="*.java" .
2. CodeQL Structural Search
If a detection signature exists in the attack pattern registry, run it:
codeql query run \
--database=piolium/codeql-artifacts/db/ \
--output=piolium/tmp/variant-search.bqrs \
-- piolium/codeql-queries/on-demand-variant-<slug>.ql
codeql bqrs decode --format=json piolium/tmp/variant-search.bqrs
3. Sibling Component Check
If the confirmed finding is in component A, check components B, C, D that share the same:
- Trust boundary
- Data flow pattern
- Framework usage
- Dependency
4. Alternate Transport Check
If the confirmed finding is via HTTP, check the same logic via:
- WebSocket
- gRPC
- GraphQL
- CLI interface
- Background job/queue consumer
Output
Write each variant candidate to its own file:
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.
- 5d ago First seen · 111 lines · 50 tokens per session scan A 870c72f4cdcf
variant-scout is an agent published in the GitHub repository vigolium/piolium (134 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 903 once invoked, about $0.0003 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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.