offensive-reporting skillA
offensive-reporting is agent-read markdown (skill) from snailsploit/claude-red: Penetration test and red team report writing methodology. Covers executive summary structuring (risk-led narrative for non-technical readers), technical finding format (title, severity, affected scope, narrative, reproduction steps, impact, remediation, references), CVSS v3.1 / v4.0 scoring with vector justification, OWASP risk rating, evidence hygiene (redacting credentials, hashing client data, time-stamping every action), screenshot and PoC artifact management, finding chain narratives, scope.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Penetration Test Reporting — Professional Methodology A great finding lost in a bad report is a wasted finding. Reports are the artifact the client pays for, the auditor reads, and the developer fixes from. Treat the report with the same rigor as the exploit. ## Quick Workflow 1. Capture evidence as you exploit — never reconstruct after the fact 2. Draft each finding immediately while context is fresh; one finding = one numbered file 3. Build the executive summary last, after all findings are scored 4. Two-pass review: technical accuracy first, then read-as-CISO for narrative 5. Hand off with a retest plan and a JSON/CSV index for the client's tracking system --- ## Report Structure (Standard) ``` 1. Executive Summary ← Last to write, first read 2. Engagement Overview 2.1 Scope 2.2 Methodology 2.3 Limitations / Assumptions 2.4 Timeline 2.5 Team 3. Risk Summary ← Heatmap, finding count by severity 4. Technical Findings ← One per finding, sorted by severity 5. Attack Narratives / Chains ← Critical chains called out separately 6. Strategic Recommendations ← Programmatic, not finding-by-finding 7. Appendices …
Read the whole file at its exact version.
How to install
mdr add snailsploit/claude-red/offensive-reporting@git:20260506.70e0c89mdr add snailsploit/claude-red/offensive-reporting@sha256:b9a8bf71828399c7Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_szzallkdizkvw55j)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14720 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
snailsploit/claude-red · 6,831 stars · license MIT · pushed 2026-09-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_szzallkdizkvw55j GET https://markdownregistry.com/api/v1/resolve?ref=snailsploit/claude-red/offensive-reporting GET https://markdownregistry.com/api/v1/blob/b9a8bf71828399c75c6c877e0768e4f916adbea352010e2fed06e57f06786200
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from snailsploit/claude-red
Every file in snailsploit/claude-red