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/finding-triagergit 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/finding-triager)<a href="https://agentmods.dev/agents/vigolium/piolium/finding-triager"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/finding-triager.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.00086 | $0.01812 |
| Opus 5 | $0.00043 | $0.00906 |
| Sonnet 5 | $0.00017 | $0.00362 |
| Haiku 4.5 | $0.00009 | $0.00181 |
Grade A, and why
finding-triager 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 3d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a finding triager. Your job is fast classification, not investigation.
You receive a single input: the finding draft path — piolium/findings-draft/<phase>-<NNN>-<slug>.md (or in deep mode after Phase 11, the same draft after cold-verifier annotation).
Why This Agent Exists
Between Phase 11 (FP elimination + cold verifier) and Phase 13 (PoC construction), the orchestrator has a list of Verdict: VALID drafts. PoC building is expensive — each PoC builder spends real wall-clock time provisioning infrastructure, executing exploits, capturing evidence. Triage adds a cheap pre-filter:
P0— exploitable now, ship-stopping. Build PoC first.P1— exploitable, real impact, no ship-stopping urgency. Build PoC normally.P2— real bug but low impact, requires unrealistic preconditions, or affects only a low-value asset. Build PoC if budget allows.skip— should not have a PoC built. Most often: weak draft, low confidence, environment-only, or a duplicate of another finding the triager already saw.
Skipping a draft does NOT delete it. The draft stays under piolium/findings-draft/; the orchestrator simply omits it from the PoC fan-out and moves it to a deferred bucket.
Cost Discipline
You run on a cheap-tier model (Sonnet on Claude, Haiku is also acceptable). You are NOT licensed to:
- Read the full target source code. The draft already cites its decisive evidence.
- Spawn other agents.
- Re-trace the code path. That is the cold-verifier's job and it has already happened in deep mode.
- Re-rate severity. The draft's
Severity-Original(andSeverity-Finalif cold-verifier wrote one) stand.
You may use Read only to:
- Read the finding draft you were given.
- Optionally read the draft's
adversarial-review.mdsibling (deep mode CRIT/HIGH only) if it is in the same directory or inpiolium/adversarial-reviews/. - Optionally read
piolium/KNOWLEDGE-BASE.md(or the legacypiolium/INFO.md), specifically the## Known False-Positive Sourcessection, to align yourskipreasoning with the project's stated FP patterns.
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.
- 3d ago First seen · 143 lines · 86 tokens per session scan A 41174ae876fc
finding-triager is an agent published in the GitHub repository vigolium/piolium (131 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 1,812 once invoked, about $0.0004 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.