report-writer — Claude Code subagent: pentest reports
The report-writer subagent for Claude Code compiles vulnerability findings into reports for pentests, bounty submissions, and technical writeups.
no license ★ 1,298 updated 2026-06-12
.claude/agents/report-writer.mdWhat report-writer does
This subagent takes a list of vulnerabilities and generates structured reports for bug bounty platforms, penetration tests, or public disclosure. Before writing, it searches for similar closed reports via the writeup-search MCP tool to check how titles are phrased, what CVSS vectors were accepted, and what remediation wording worked. This increases acceptance rate.
The subagent reads rules/mistakes.md to avoid common pitfalls: no CWE-200 as primary CWE (too generic), no HackerOne titles over 80 characters, file paths verified with ls before insertion. Requirements: file reading, Markdown writing, ls and grep execution. Reports must include Summary, Host, Endpoints, Steps, Impact, Remediation, CVSS with per-metric justification, CWE and CAPEC. Without access to vulnerability sources, nothing to generate.
What it helps with
- compile pentest report from findings with risk-sorted sections
- write HackerOne or Bugcrowd submission following platform template
- generate writeup with CVSS justification and CWE for public disclosure
- verify CVSS vector and CWE before submission to avoid CWE-200
- find similar closed report and extract remediation phrasing
Example prompts for the agent
- Build a bounty report from findings in
findings/for HackerOne, CVSS 3.1 - Write a pentest report with executive summary and risk matrix from
vulns/ - Create a technical writeup for the IDOR issue in
reports/drafts/idor-notes.md
How to install report-writer
Manually: put the files in place
.claude/agents/report-writer.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/report-writer.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/report-writer.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about report-writer
How to install report-writer in Claude Code?
Copy the subagent file to .claude/agents/report-writer.md in the project root.
What does report-writer do?
The subagent generates security reports from vulnerability findings: bug bounty submissions, pentest documents, technical writeups. It searches for similar closed reports via the writeup-search MCP server, checks phrasing templates, and avoids common mistakes like CWE-200 or overly long titles.
Why does report-writer search old reports before writing?
Bounty platforms accept reports faster when structure and wording match successful closed submissions. The subagent reads 2–3 writeups, extracts title format, impact phrasing, and remediation recommendations.