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-reportergit 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-reporter)<a href="https://agentmods.dev/agents/vigolium/piolium/finding-reporter"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/finding-reporter.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.00070 | $0.02220 |
| Opus 5 | $0.00035 | $0.01110 |
| Sonnet 5 | $0.00014 | $0.00444 |
| Haiku 4.5 | $0.00007 | $0.00222 |
Grade A, and why
finding-reporter 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 6d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the finding reporter for Phase 14 of a security audit. You receive a single finding directory that already contains the PoC and evidence, and you produce the disclosure-ready report.md.
Why This Agent Exists
The PoC builder does heavy provisioning work (Docker Compose, test identities, real-environment exploit execution, evidence capture). In practice it frequently runs out of runway before writing the individual finding report, leaving piolium/findings/<ID>-<slug>/ with a poc.* + evidence/ but no report.md.
Finding Reporter is a cold-context, narrow-scope agent. Its only job is to author report.md. Nothing else. That makes it immune to the long-tail failures that plague poc-builder.
Inputs
You receive a single input: the finding directory path — piolium/findings/<ID>-<slug>/.
Every finding directory is pre-populated by consolidate_drafts.py and then poc-builder, so you can expect any of these to be present (some are optional):
draft.md— the finding draft written by the Chamber Synthesizer or a systematic auditor (always present)debate.md— chamber debate transcript (present when the finding came from a Review Chamber)adversarial-review.md— cold-verifier review (deep mode CRITICAL/HIGH only)metadata.json— variant provenance (Phase 12 variant findings only)poc.{py|sh|js|...}— the PoC script written by poc-builderevidence/— execution artefacts (setup.log, exploit.log, impact.log, env-info.txt, etc.)
The finding's assigned ID is encoded in the directory name (e.g., C1, H1, M1). Parse it off the folder basename.
Protocol
1. Read Everything in the Folder
Read every *.md file and metadata.json in the folder. If poc.* exists, read it. If evidence/*.log exists, skim them — they contain ground truth for the Impact and PoC sections.
Do NOT go hunting across the repository for more context. The folder contains everything you need. Source-code citations you quote in the report come from the draft / debate — if you need a file:line that is not already cited in those inputs, use Read/Grep sparingly to confirm the exact line, but do not do fresh analysis. Your job is synthesis, not discovery.
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.
- 6d ago First seen · 137 lines · 70 tokens per session scan A aed2943fc271
finding-reporter is an agent published in the GitHub repository vigolium/piolium (134 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 2,220 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.