report

report is a command for coding agents from ByamB4/find-cve-agent. It costs 33 tokens per session (1,124 once invoked), scanned A, original, Apache-2.0.

A command that turns a confirmed software vulnerability into a disclosure report for the project maintainer.

In plain words
What is it for?
Run /report after confirmation, a working proof of concept, and a CVSS score to prepare a report for HackerOne, GitHub, email, or another available channel.
Why use it?
It gathers the technical evidence and selects a suitable reporting channel, reducing the work needed to explain the issue responsibly.

Command

Part of the find-cve-agent plugin — 21 skills, 7 commands, 5 agents shipped together

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.

agentmods
npx agentmods add commands/byamb4/find-cve-agent/report
Clone the repo
git clone --depth 1 https://github.com/ByamB4/find-cve-agent

Or install find-cve-agent, the plugin that ships this one along with the rest of its 21 skills, 7 commands, 5 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.

agentmods badge for report

README.md
[![agentmods](https://agentmods.dev/badge/commands/byamb4/find-cve-agent/report.svg)](https://agentmods.dev/commands/byamb4/find-cve-agent/report)
Your own site
<a href="https://agentmods.dev/commands/byamb4/find-cve-agent/report"><img src="https://agentmods.dev/badge/commands/byamb4/find-cve-agent/report.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 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,124 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
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.00033 $0.01124
Opus 5 $0.00016 $0.00562
Sonnet 5 $0.00007 $0.00225
Haiku 4.5 $0.00003 $0.00112

Measured 5d ago against content hash 0fd433f6a75d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

report scanned grade A 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 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s "https://hackerone.com/directory/programs" | grep -i "<project>"
commands/report.md · 197 lines

How it starts

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

/report

Generate a professional disclosure report for a confirmed vulnerability finding.

Prerequisites

  • Finding must be CONFIRMED by the Validator (verdict.md exists with CONFIRMED)
  • PoC must be working (poc_*.py exits 0)
  • CVSS score must be calculated

Process

Step 1: Gather Finding Details

Read from the target directory:

  • targets/<repo>/findings.md for technical details
  • targets/<repo>/verdict.md for confirmation
  • targets/<repo>/poc_<vuln_type>.py for the PoC header
  • targets/<repo>/brief.md for project info

Step 2: Determine Disclosure Channel

Check in priority order:

  1. HackerOne: Search for the project

    curl -s "https://hackerone.com/directory/programs" | grep -i "<project>"
    

    If found -> use HackerOne format

  2. GitHub Security Advisory: Check if repo has advisories enabled

    gh api "repos/<owner>/<repo>" --jq '.has_security_policy // false'
    

    If true -> use GHSA format

  3. SECURITY.md: Check for security contact

    gh api "repos/<owner>/<repo>/contents/SECURITY.md" --jq '.content' | base64 -d 2>/dev/null
    

    If exists -> use email format

  4. Package maintainer email: Check package registry

    npm view <package> maintainers --json 2>/dev/null
    

    If found -> use email format

  5. GitHub Issue: Last resort

Step 3: Generate Report

GitHub Security Advisory Format
## Summary

[Vulnerability Type] in [package-name] [component] allows [impact description].

## Details

**Affected package**: [name]
**Affected versions**: [version range, e.g., "<= 3.2.1"]
**Patched version**: None (0-day)

### Root Cause

[Technical description of the vulnerability. Include the file path and line number.
Explain why the current code is vulnerable and what an attacker can do.]

### Attack Vector

[Step-by-step description of how an attacker would exploit this.]

1. [Step 1]
2. [Step 2]
3. [Step 3]

### Impact

[What an attacker can achieve. Be specific: read files, execute commands, etc.]

## Proof of Concept

[PoC code or steps to reproduce]

## Severity

**CVSS**: [vector string] = [score] [severity]
**CWE**: [CWE-XXX] ([name])

## Suggested Fix

[Specific recommendation for how to fix the vulnerability.
Include code examples if possible.]

## Timeline

- [Date]: Vulnerability discovered
- [Date]: Report submitted via [channel]
- [Date + 90 days]: Planned public disclosure (if no response)

Read the full file on GitHub · 197 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. 5d ago First seen · 197 lines · 33 tokens per session scan A 0fd433f6a75d

Subscribe to this mod's changes

report is a command published in the GitHub repository ByamB4/find-cve-agent (47 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,124 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.