report

Files (1)

• SKILL.md

SKILL.md (first lines)

# Report Generator

## Overview

Reads `triage.md` (required) and `session.json` to produce a structured report.
80-90% of content is pre-filled from `report_draft.findings[]` - this skill formats and narratizes, it does not discover.

## Steps

1. **Get target and report mode from user if not provided.**
   - Ask: "Full pentest report or Bug Bounty submission format (HackerOne/Bugcrowd)?"

2. **Read triage.md (required):**
   ```bash
   cat ~/pentest-toolkit/results/<target>/triage.md
   ```
   If missing: stop and tell the user to run `/triage <target>` first.

3. **Read session.json for Scalpel stats:**
   ```bash
   SESSION=~/pentest-toolkit/results/<target>/session.json
   SCALPEL_SCORE=$(jq -r '.scalpel.snr.scalpel_score // "N/A"' $SESSION 2>/dev/null)
   CERTIFIED=$(jq '.report_draft.findings | map(select(.status=="SCALPEL_CERTIFIED")) | length' $SESSION 2>/dev/null)
   ```

4. **Read plan.md (optional):**
   ```bash
   cat ~/pentest-toolkit/results/<target>/plan.md 2>/dev/null
   ```

5. **Get today's date:**
   ```bash
   date +%Y-%m-%d
   ```

6. **Write report** to `~/pentest-toolkit/results/<target>/report-<YYYY-MM-DD>.md`:

```markdown
# Penetration Test Report: <target>
**Date:** <YYYY-MM-DD>
**Assessor:** Akira / Red Team

---

## Scalpel Assessment Quality

| Metric | Value |
|--------|-------|
| Scalpel Score | <N>/100 |
| Certified Findings (SCL) | <N> |
| False Positives | 0 |
| KCCG Complete | <N>/<N> |

> Every finding below is Scalpel Certified — 5-layer Precision Gate passed,
> full Kill Chain proven, DNA fingerprinted, PoC generated.

---

## Executive Summary
**Scope:** <from plan.md, or "Quick engagement — no scope document recorded">
**Assessment Period:** <date>

<2-3 sentence summary of most critical certified findings and overall risk posture>

**Findings Summary:**

| Severity | SCL Certified | Potential |
|----------|--------------|-----------|
| Critical | <N> | <N> |
| High | <N> | <N> |
| Medium | <N> | <N> |
| Low | <N> | <N> |

---

## Certified Findings

### [SCL-YYYY-NNN] <Title>

```
SCALPEL CERTIFIED  [SCL-YYYY-NNN]
Severity:    <Critical|High|Medium|Low>
KCCG:        <N>/5  (<severity> certified)
Confidence:  <N> / 100
DNA:         <hash truncated>...
PoC:         pocs/<SCL-YYYY-NNN>_poc.sh
```

**Severity:** <severity>
**CVSS Estimate:** <score> (AV:N/AC:L/PR:N/UI:N/...)
**Asset:** <affected endpoint>
**Weakness:** CWE-<N> — <name>

**Description:** <what the vulnerability is>

**Kill Chain:**
1. <step 1: technique and action>
2. <step 2: technique and action>
3. <step 3: technique and action>

**Impact:** <business impact — specific: "An attacker can extract AWS IAM credentials and access production S3 buckets containing customer database backups">

**Evidence:**
```
<direct HTTP response quote or tool output — must be from kill_chain evidence>
```

**Steps to Reproduce:**
```bash
# See pocs/<SCL-YYYY-NNN>_poc.sh for full reproduction script
# Key commands:
<step 1 command>
<step 2 command>
```

**Remediation:** <specific actionable fix>

---

From kalpmodi/akira, MIT.

More from kalpmodi/akira