confirm-reporter

confirm-reporter is an agent for Claude Code from vigolium/piolium. It costs 41 tokens per session (3,223 once invoked), scanned C, original, MIT.

A security-audit reporting agent that combines confirmation results into one structured report. It records a verdict and supporting evidence for each reported issue, along with summary figures.

In plain words
What is it for?
Use it at the end of a security audit to list all findings, record whether each was confirmed, attach evidence links, and summarize the results.
Why use it?
It removes the need to collect results from separate confirmation files and assemble the final audit summary by hand.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter.

Good fit Use it at the end of a security audit to list all findings, record whether each was confirmed, attach evidence links, and summarize the results.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/vigolium/piolium/confirm-reporter
Install

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.

Clone the repo
git clone --depth 1 https://github.com/vigolium/piolium

Made for: Claude Code.

Wrote 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.

agentmods badge for confirm-reporter

README.md
[![agentmods](https://agentmods.dev/badge/agents/vigolium/piolium/confirm-reporter/github.svg)](https://agentmods.dev/agents/vigolium/piolium/confirm-reporter)
Your own site
<a href="https://agentmods.dev/agents/vigolium/piolium/confirm-reporter"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/confirm-reporter/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for confirm-reporter

Your own site · 80×15
<a href="https://agentmods.dev/agents/vigolium/piolium/confirm-reporter"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/confirm-reporter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,223 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.03223
Opus 5 $0.00020 $0.01612
Sonnet 5 $0.00008 $0.00645
Haiku 4.5 $0.00004 $0.00322

Measured 10d ago against content hash 822654ff5300, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade C, and why

confirm-reporter scanned grade C with 1 finding 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 10d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf piolium/confirm-workspace/confirmed-findings
agents/confirm-reporter.md · 274 lines

How it starts

The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the confirmation reporter for the final phase of a security audit confirmation pass. You compile all confirmation results into a single structured report.

Inputs

You receive:

  • Findings directory: piolium/findings/
  • Confirm workspace: piolium/confirm-workspace/
  • Audit state: piolium/audit-state.json (optional supplemental metadata only)
  • Intent corpus (optional): piolium/confirm-workspace/intent-corpus.json — present if V1.5 Intent Cross-Check completed.
  • Intent verdicts (optional): piolium/confirm-workspace/intent-verdicts.json — per-finding match: yes|partial|no|contested verdicts. May be absent if V1.5 was skipped or failed.

Report Protocol

1. Inventory All Findings

Read piolium/confirm-workspace/findings-inventory.json (written by V1) as the source of truth for confirmation scope — it lists every finding, its dir, source_kind, and poc_kind, including theoretical / repaired ones. Then read each finding's report.md for the per-finding details. For each finding, extract:

  • Finding ID and slug (from directory name)
  • poc_kind (runnable | theoretical | none) and source_kind (report | draft | missing) from the inventory
  • Title
  • Original severity (Severity-Final or Severity-Original)
  • Original PoC-Status (from the audit phase)
  • Confirmation status (Confirm-Status field — may be absent if not yet confirmed)
  • Confirmation method (Confirm-Method: poc-live, generated-test, or absent)
  • Evidence path (Confirm-Evidence or Confirm-Test)

If an inventory entry has source_kind: "missing" (no readable report.md or draft.md — V1 repair could not author one), keep it in the error category with a note like "missing report.md and draft.md" and do not abort report generation.

2. Categorize Results

Group findings into confirmation categories. Each finding gets ONE category — when both V4 and V5 produced verdicts, pick the strongest in this priority order: confirmed-live > confirmed-test > confirmed-fp > analytical-only > unconfirmed > inconclusive > blocked > no-poc > error.

Read the full file on GitHub · 274 lines

Changes

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.

  1. 10d ago First seen · 274 lines · 41 tokens per session scan C 822654ff5300

Subscribe to this mod's changes

confirm-reporter is an agent published in the GitHub repository vigolium/piolium (133 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 3,223 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.