agentleFS
fatihkanfatihkan/badi/.claude/skills-vault/pentest-engagement/SKILL.md

pentest-engagement

Skill8 starsChanged 3 months agoMITView on GitHub

Penetration testing engagement planning — scoping, ROE drafting, phased timeline, MITRE ATT&CK mapping, kickoff/closeout documentation. Triggers on engagement plan, ROE, rules of engagement, scoping, pentest plan, phased plan, MITRE mapping, attack matrix, kickoff, closeout.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create at the start of the engagement:

    line 112

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

pentest-engagement

Produces planning + scoping + ROE documentation for an authorized penetration testing engagement.

Triggers

  • "prepare a pentest plan"
  • "draft the ROE"
  • "scoping document"
  • "engagement timeline"
  • "MITRE ATT&CK matrix"
  • "kickoff meeting agenda"
  • "closeout report template"

Deliverables

  1. Scope Document (in-scope, out-of-scope, constraints)
  2. Rules of Engagement (ROE) (forbidden techniques, working hours, escalation path)
  3. Phased Timeline (kickoff -> recon -> exploit -> post-ex -> reporting -> closeout)
  4. MITRE ATT&CK Mapping (Tactic + Technique list per phase)
  5. Communication Plan (client contact, escalation contact, incident response)
  6. Acceptance Criteria (tests covered, reporting, deliverable list)

Scope Document Template

# Engagement Scope — <Client>

## In-Scope
- IP Ranges: 10.0.0.0/16, 192.168.50.0/24
- Domains: *.example.com, app.example.com
- Cloud Accounts: AWS 123456789012 (production us-east-1)
- Test Type: External / Internal / Web App / Cloud / Red Team

## Out-of-Scope
- Production DB direct query
- Email/Phishing a client employee
- DoS / stress testing
- 3rd party SaaS (Stripe, SendGrid, etc.)

## Restrictions
- Working hours: Weekdays 09:00-17:00 (TR)
- Aggressive scan: Only within a user-approved window
- Data exfil: None — evidence files only (max 1MB)

## Authorization
- Letter of authorization: <link>
- Client signature: <name, date>
- Pentest firm signature: <name, date>

Phased Plan Template (5 Phase)

PhaseDurationActivityMITRE Tactic
1. Recon1-2 daysOSINT, subdomain enum, port scanTA0043 Reconnaissance
2. Initial Access2-3 daysWeb app exploit, phishing sim, AD attackTA0001 Initial Access
3. Post-Exploit3-4 daysPrivesc, lateral, persistence, exfil simTA0004/TA0008/TA0003/TA0010
4. Detection1-2 daysSIEM/EDR coverage gapTA0042 Resource Development (defensive)
5. Report2-3 daysFinding writeup, CVSS, remediation, debrief—

MITRE ATT&CK Mapping

State at least 1 ATT&CK Technique ID per finding (T1059, T1078, etc.). Mapping:

finding: SQL Injection in /api/users
mitre:
  tactic: TA0001 (Initial Access)
  techniques:
    - T1190 (Exploit Public-Facing Application)
detection:
  - Sigma rule: web/sql_injection.yml
remediation:
  priority: P0
  effort: 8h

Kickoff Meeting Agenda (1 hour)

  1. Scope review + signoff (10 min)
  2. ROE walkthrough + restrictions (15 min)
  3. Communication channel + escalation (10 min)
  4. Asset inventory hand-off (15 min)
  5. Q&A + first-day planning (10 min)

Closeout Meeting Agenda (1.5 hours)

  1. Executive summary (10 min)
  2. Top 3 critical finding walkthrough (30 min)
  3. Remediation roadmap (20 min)
  4. Detection rule hand-off (15 min)
  5. Lessons learned (15 min)

Output Location

Create at the start of the engagement:

engagements/<client>-<yyyymmdd>/
  scope.md
  roe.md
  timeline.md
  mitre-mapping.yml
  contacts.md

Out-of-Scope (This Skill Does Not Do)

  • Live command composing (pentest-recon, pentest-web, etc. do that)
  • Producing exploit guides (pentest-exploit-chain does that)
  • Report writing (pentest-report does that)

This skill produces planning + scoping docs only.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.