/report
Generate a formatted vulnerability report from engagement findings
$ npx -y skills add ogrodev/fsociety --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/report
Context preview
What this command does when you run it.
Generate a formatted vulnerability report from engagement findings
Command definition
report.mddescription: Generate a formatted vulnerability report from engagement findings
allowed-tools: ToolSearch, Bash, Read, Write, Glob, Grep
argument-hint:
> **Storage Policy**: ALL output files MUST be saved in the project directory. NEVER write to `/tmp/` or any system temporary directory.
Generate Vulnerability Report
Generate a comprehensive penetration test report from findings in the current engagement.
Step 1: Load Tools
Use ToolSearch to load:
- `create_vulnerability_report` — formatted vulnerability report generation
- `create_scan_summary` — scan result summarization
Step 2: Gather Findings
Read all reconnaissance and scan output files in the project directory:
- Use Glob to find `*.md` files in the current directory and subdirectories
- Look for ATTACK-VECTORS.md, VULNERABILITY-REPORT.md, or similar
- Read scan outputs (webscan-*, apiscan-*, portscan-*, etc.)
- Check `reports/` subdirectory for detailed findings
Step 3: Scan Summary
Run `create_scan_summary` to generate a consolidated summary of all tool outputs from this engagement.
Step 4: Vulnerability Report
Run `create_vulnerability_report` with all discovered vulnerabilities, organized by:
- CVSS severity (Critical → Info)
- Vulnerability type (injection, auth, config, etc.)
- Each finding should include:
- Title and description
- Affected endpoint/component
- Steps to reproduce
- Evidence/proof
- Impact assessment
- Remediation recommendation
Step 5: Output
Save the report to `PENTEST-REPORT-{date}.md` in the project directory.
Include:
- Executive summary
- Scope and methodology
- Findings by severity
- Risk matrix
- Remediation priority list
Read more
description: Generate a formatted vulnerability report from engagement findings allowed-tools: ToolSearch, Bash, Read, Write, Glob, Grep argument-hint:
> **Storage Policy**: ALL output files MUST be saved in the project directory. NEVER write to `/tmp/` or any system temporary directory.
Generate Vulnerability Report
Generate a comprehensive penetration test report from findings in the current engagement.
Step 1: Load Tools
Use ToolSearch to load:
- `create_vulnerability_report` — formatted vulnerability report generation
- `create_scan_summary` — scan result summarization
Step 2: Gather Findings
Read all reconnaissance and scan output files in the project directory:
- Use Glob to find `*.md` files in the current directory and subdirectories
- Look for ATTACK-VECTORS.md, VULNERABILITY-REPORT.md, or similar
- Read scan outputs (webscan-*, apiscan-*, portscan-*, etc.)
- Check `reports/` subdirectory for detailed findings
Step 3: Scan Summary
Run `create_scan_summary` to generate a consolidated summary of all tool outputs from this engagement.
Step 4: Vulnerability Report
Run `create_vulnerability_report` with all discovered vulnerabilities, organized by:
- CVSS severity (Critical → Info)
- Vulnerability type (injection, auth, config, etc.)
- Each finding should include:
- Title and description
- Affected endpoint/component
- Steps to reproduce
- Evidence/proof
- Impact assessment
- Remediation recommendation
Step 5: Output
Save the report to `PENTEST-REPORT-{date}.md` in the project directory.
Include:
- Executive summary
- Scope and methodology
- Findings by severity
- Risk matrix
- Remediation priority list
Multi-plugin marketplace for Claude Code offensive security plugins
Repo: ogrodev/fsociety
Other commands on fsociety.
- /apiscan
API security audit — REST, GraphQL, JWT analysis, parameter discovery
Open command - /archives
Archive or list previous engagement snapshots
Open command - /bruteforce
Password brute force and hash cracking against target services
Open command - /campaign
Resume or execute an attack campaign with progress tracking
Open command - /dashboard
Show running scans, system health, and engagement status
Open command - /debrief
Post-engagement lessons learned analysis and debrief report
Open command

