redteam-report-generation skillA
redteam-report-generation is agent-read markdown (skill) from miosa-osa/osa: Engagement report generation for red-team and pentest work: severity-ordered finding sections with verification status badges, evidence snippets with type labels, CVE/CWE cross-references, remediation guidance, mission metadata (status, phases, timestamps), markdown escaping for safe report rendering, and best-effort report writing that never breaks the engagement. Use when writing the final report for a security engagement, structuring findings for delivery, or generating status reports from a .
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
# Red-Team Report Generation Derived from T3MP3ST's `src/reporting/auto-report.ts` (Apache-2.0). A report is the engagement's deliverable — structure it so severity, verification status, and evidence are visible at a glance, and write it best-effort so reporting never breaks the mission. ## 1. Report skeleton ```markdown # Engagement Report: <mission name> - **Status**: <status> - **Final phase**: <phase> - **Started**: <ISO-8601> - **Completed**: <ISO-8601 or —> ## Targets - <address> (<type>, zone: <zone>, status: <status>) ## Findings (<total>) ### CRITICAL (n) - **[CRITICAL] <title>** — ✅ verified | ⚠️ unverified (<provenance>) - Description: ... - CVE: CVE-XXXX-YYYY - CWE: CWE-ZZZ - Remediation: ... - Evidence (output): `<snippet ≤180 chars, whitespace-collapsed>` ### HIGH (n) ... ## Methodology <what was done, in order, with tool versions> ``` ## 2. The rules that make the report honest - **Severity ordering is fixed**: critical → high → medium → low → info. Every finding appears under its severity heading with a count. - **Verification status is stamped on every finding**: `✅ verified` when the …
Read the whole file at its exact version.
How to install
mdr add miosa-osa/osa/redteam-report-generation@git:20260913.e13b6b8mdr add miosa-osa/osa/redteam-report-generation@sha256:e99099a320e4d80bPin 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_i2pbrhg6bvsp5v7t)
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 (4469 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
miosa-osa/osa · 74 stars · license NOASSERTION · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_i2pbrhg6bvsp5v7t GET https://markdownregistry.com/api/v1/resolve?ref=miosa-osa/osa/redteam-report-generation GET https://markdownregistry.com/api/v1/blob/e99099a320e4d80b2c575ee4fdef654710733f7233c7825316bb7bfd4ca8f944
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.