A command that turns validated security findings into a bug bounty report for HackerOne, Bugcrowd, Intigriti, or Immunefi. A bug bounty report explains a vulnerability, its impact, how to reproduce it, and how to fix it.

Use /report after /validate to create a report with a title, CVSS 3.1 severity score, proof-of-concept requests and responses, impact, remediation, and supporting materials.

It removes the need to format the same technical evidence separately for each reporting platform, while requiring validation first.

report — Command by Zyrexnn

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/zyrexnn/cybermes/report

Clone the repo

git clone --depth 1 https://github.com/Zyrexnn/Cybermes

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

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

Security scan A 0 findings. Scan, not verified.

Origin 86% copy Near-identical to another mod 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	$0.00000	$0.00930
Opus 5	$0.00000	$0.00465
Sonnet 5	$0.00000	$0.00186
Haiku 4.5	$0.00000	$0.00093

Measured yesterday against content hash e23eafa39e09, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

Origin

This is a copy

86% identical to report — 23 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

knowledge/Claude-BugHunter/commands/report.md · 117 lines

How it starts

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

name: report description: Write a submission-ready bug bounty report. Generates H1/Bugcrowd/Intigriti/Immunefi format with CVSS 3.1 score, proof of concept, impact statement, and remediation. Run /validate first. Usage: /report

/report

Generate a submission-ready bug bounty report.

Pre-Conditions

Run /validate first. All 4 gates must pass before running this command.

Never write a report before validating. N/A submissions hurt your validity ratio.

Usage

/report

Provide when prompted:

Platform (HackerOne / Bugcrowd / Intigriti / Immunefi)
Bug class
Affected endpoint
Your two test accounts and their IDs
The exact HTTP request that demonstrates the bug
The exact response that shows the impact
Tech stack (for CVSS and remediation advice)

What This Generates

Title following the formula: [Bug Class] in [Endpoint] allows [actor] to [impact]
Summary paragraph (impact-first, no "could potentially")
Vulnerability details with CVSS 3.1 score and vector string
Steps to Reproduce with copy-paste HTTP requests
Impact statement with quantification
Recommended fix (1-2 sentences, specific)
Supporting materials section

Platform Selection

HackerOne Format

Markdown sections: Summary, Vulnerability Details, Steps to Reproduce, Impact, Recommended Fix
Include CVSS 3.1 score + vector string
Include two test account setup instructions
Keep under 600 words

Bugcrowd Format

Title with VRT category: [VRT Category] > [Subcategory] > P[1-4]
Expected vs Actual Behavior section
Severity Justification section referencing Bugcrowd VRT

Intigriti Format

CVSS score prominent at top
Clear reproduction steps
Business impact focused

Immunefi Format (Web3)

Root cause in Solidity code
Foundry PoC test included
Economic impact quantified in $ value
Comparison evidence (same check present elsewhere, missing here)

Writing Rules

Never use: "could potentially", "may allow", "might be possible"
Always prove: show actual data/action, not just "200 OK"
Impact first: sentence 1 = what attacker gets, not what the bug is
Quantify: how many users affected, what data type, $ amount
Short: triagers skim. < 600 words.
Human: write to a person, not a system

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

yesterday First seen · 117 lines · 0 tokens per session scan A e23eafa39e09

Subscribe to this mod's changes

report is a command published in the GitHub repository Zyrexnn/Cybermes (668 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 930 tokens. A static security scan graded it A with 0 findings. It is 86% identical to report, differing in 23 lines, and is treated as a copy.

Debugging Security ai-agent appsec bug-bounty cybersecurity devsecops exploit-validation

report