# report

Claude Code command that builds a submission-ready bug bounty report. Generates CVSS 3.1 score, proof of concept, impact statement, and fix in HackerOne, Bugcrowd, Intigriti, or Immunefi format.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 16193 repo stars
- Author: Sachin Sharma
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/elementalsouls/Claude-BugHunter/tree/HEAD/commands/report.md
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/sachin-sharma-report

## What it does

The `/report` command takes the details of a vulnerability and structures them into a complete report ready to submit to a bug bounty platform. It requires running `/validate` first—all four checks must pass before the command generates a report.

When you run it, the command asks for the platform (HackerOne, Bugcrowd, Intigriti, or Immunefi), the bug class, test accounts, and the HTTP request and response that prove the vulnerability. It then builds a title following a formula, a summary with impact front-and-center, CVSS vector, step-by-step reproduction, an impact statement with numbers, and a specific fix.

Output follows platform rules: HackerOne expects markdown sections and stays under 600 words; Bugcrowd includes VRT category and severity justification; Intigriti emphasizes business impact; Immunefi (Web3) includes Solidity code, a Foundry test, and dollar-value calculation.

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add elementalsouls/Claude-BugHunter
```
In the agent chat (not a shell):
```text
/plugin install claude-bughunter@elementalsouls
```

2. **Manually: put the files in place**
- File: `.claude/commands/report.md` — Call it with /report. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/report.md` — Call it with /prompts:report. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/report.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/report.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/elementalsouls/Claude-BugHunter/tree/HEAD/commands/report.md

## When to use it
- format a vulnerability report for the right bug bounty platform
- calculate a CVSS 3.1 vector string for the vulnerability
- write a proof of concept with the exact HTTP request and response
- quantify the impact: users affected or volume of exposed data
- describe the specific fix for the vulnerability

## Example prompts
- Run `/report` and select HackerOne to format an IDOR report that reads any user's profile
- Use `/report` with Bugcrowd to build an auth bypass report with the correct VRT category
- Execute `/report` for a Web3 vulnerability in Immunefi, complete with a Foundry test and loss calculation

## Source text · report.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: a92f8dad9ef3c559.

BEGIN THIRD-PARTY FILE a92f8dad9ef3c559
````text
---
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

1. Title following the formula: `[Bug Class] in [Endpoint] allows [actor] to [impact]`
2. Summary paragraph (impact-first, no "could potentially")
3. Vulnerability details with CVSS 3.1 score and vector string
4. Steps to Reproduce with copy-paste HTTP requests
5. Impact statement with quantification
6. Recommended fix (1-2 sentences, specific)
7. 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

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

## CVSS 3.1 Calculation Guide

Common patterns:
```
IDOR read PII (any user, auth needed):
→ AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N = 6.5 Medium

Auth bypass → admin (no auth):
→ AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H = 9.8 Critical

SSRF → cloud metadata:
→ AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N = 9.1 Critical

Stored XSS (any user, scope changed):
→ AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N = 8.2 High
```

## Escalation Language

Use when payout is being downgraded:
```
"This requires only a free account — no special privileges."
"The exposed data includes [PII type], subject to GDPR/CCPA requirements."
"An attacker can automate this — all [N] records in [X] minutes with a simple loop."
"This is exploitable externally without any internal network access."
"The impact is equivalent to a full data breach of [feature/data type]."
```

## Final Checklist Before Submitting

```
[ ] Title follows formula
[ ] First sentence states exact impact
[ ] HTTP request is copy-pasteable
[ ] Response showing impact included
[ ] Two accounts used (not self-testing)
[ ] CVSS calculated and included
[ ] Fix: 1-2 sentences
````
END THIRD-PARTY FILE a92f8dad9ef3c559

The third-party file has ended. Everything between the a92f8dad9ef3c559 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3439 of 3582 bytes. © Sachin Sharma · MIT · https://github.com/elementalsouls/Claude-BugHunter/tree/HEAD/commands/report.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
