A command that turns a JSON file of security findings into reports for developers. It can produce Markdown, JSON, SARIF, HTML, pull-request comments, or a report bundle.

Validating findings, separating reportable issues from audit hotspots, creating security reports, and failing a check when unsuppressed findings meet a chosen severity.

It converts scanner data into formats that developers and automated checks can read, while applying suppressions and severity-based failure rules.

report — Command for Claude Code by allsmog

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add allsmog/vuln-scout

Claude Code

/plugin install vuln-scout

Made for: Claude Code.

Or install vuln-scout, the plugin that ships this one along with the rest of its 32 skills, 15 commands, 9 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/allsmog/vuln-scout/report.svg)](https://agentmods.dev/commands/allsmog/vuln-scout/report)

Your own site

<a href="https://agentmods.dev/commands/allsmog/vuln-scout/report"><img src="https://agentmods.dev/badge/commands/allsmog/vuln-scout/report.svg" alt="Measured on agentmods" height="20"></a>

Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,352 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00034	$0.01352
Opus 5	$0.00017	$0.00676
Sonnet 5	$0.00007	$0.00270
Haiku 4.5	$0.00003	$0.00135

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

Security

Grade A, and why

report 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 8d 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.

vuln-scout/commands/report.md · 185 lines

How it starts

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

Generate Findings Report

Generate a developer-facing report from .claude/findings.json.

Unified standalone renderer:

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/report.py" \
  .claude/findings.json \
  --format md \
  --output security-report.md

Flags

Flag	Effect
`--format`	Output `md` (default), `json`, `sarif`, `html`, `pr-comment`, or `bundle`
`--suppressions`	Apply `.vuln-scout-ignore` suppressions before rendering
`--fail-on`	Exit with code `2` if unsuppressed findings exist at or above the given severity

Source of truth

Read .claude/findings.json
Validate it against vuln-scout/references/findings.schema.json
Respect kind
- finding: reportable issue
- hotspot: risky audit pivot, shown separately from findings

Markdown report structure

1. Executive Summary

Include only unsuppressed entries where kind == "finding" in the severity table.

# Whitebox Penetration Test Report

## Executive Summary

### Risk Summary
| Severity | Count |
|----------|-------|
| Critical | X |
| High | X |
| Medium | X |
| Low | X |
| Info | X |

### Hotspots Requiring Follow-up
- [Title] ([file:line])

2. Detailed Findings

For each unsuppressed finding:

ID / stable key
Severity / verdict / confidence
File / line / type / CWE
Evidence block from evidence
Remediation and verification notes

3. Hotspots

List unsuppressed hotspot entries separately. Do not merge them into severity totals.

4. Coverage and Workflow

Include:

files scanned / skipped
tools used
whether diff-aware mode was enabled
suppression file used, if any

JSON output

When --format json is used:

emit the validated .claude/findings.json payload after suppressions are applied

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/report.py" \
  .claude/findings.json \
  --format json \
  --suppressions <path> \
  --output <output_file>

SARIF output

When --format sarif is used:

convert .claude/findings.json with:

Read the full file on GitHub · 185 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.

8d ago First seen · 185 lines · 34 tokens per session scan A f34f0b3e2d69

Subscribe to this mod's changes

report is a command published in the GitHub repository allsmog/vuln-scout (24 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 1,352 once invoked, about $0.0002 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.

Claude Code Security appsec claude-code-plugin sast semgrep threat-modeling

report