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
- Kur1sulab/blackboxtheir own version, first seen Aug 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Kur1sulab/blackbox★ 3same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository63 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-automationSkill
- consultingSkill
- contentSkill
- customer-successSkill
- data-analyticsSkill
- designSkill
- design-tokensSkill
- developmentSkill
- devopsSkill
- ecommerceSkill
- emailSkill
- expo-app-configSkill
- expo-config-pluginSkill
- expo-dev-clientSkill
- expo-eas-buildSkill
- expo-eas-submitSkill
- expo-eas-updateSkill
- expo-modulesSkill
- expo-notificationsSkill
- expo-orchestratorSkill
- expo-prebuildSkill
- expo-routerSkill
- expo-troubleshootingSkill
- financeSkill
- frontend-tasteSkill
- marketingSkill
- market-researchSkill
- mobileSkill
- pentest-adSkill
- pentest-apiSkill
- pentest-bizlogicSkill
- pentest-bugbountySkill
- pentest-cicdSkill
- pentest-cloudSkill
- pentest-credentialsSkill
- pentest-ctfSkill
- pentest-detectionSkill
- pentest-exploit-chainSkill
- pentest-forensicsSkill
- pentest-llmSkill
- pentest-malwareSkill
- pentest-mobileSkill
- pentest-opsec-evidenceSkill
- pentest-orchestratorSkill
- pentest-privescSkill
- pentest-reconSkill
- pentest-reportSkill
- pentest-socialSkill
- pentest-stigSkill
- pentest-threat-modelSkill
- pentest-webSkill
- pentest-wirelessSkill
- productivitySkill
- productSkill
- salesSkill
- security-checkSkill
- securitySkill
- seo-crawl-budgetSkill
- seoSkill
- The first 60 shown.
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
- Distinctive: line 112
Create at the start of the engagement:
≈ “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.
Files
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
- Scope Document (in-scope, out-of-scope, constraints)
- Rules of Engagement (ROE) (forbidden techniques, working hours, escalation path)
- Phased Timeline (kickoff -> recon -> exploit -> post-ex -> reporting -> closeout)
- MITRE ATT&CK Mapping (Tactic + Technique list per phase)
- Communication Plan (client contact, escalation contact, incident response)
- 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)
| Phase | Duration | Activity | MITRE Tactic |
| 1. Recon | 1-2 days | OSINT, subdomain enum, port scan | TA0043 Reconnaissance |
| 2. Initial Access | 2-3 days | Web app exploit, phishing sim, AD attack | TA0001 Initial Access |
| 3. Post-Exploit | 3-4 days | Privesc, lateral, persistence, exfil sim | TA0004/TA0008/TA0003/TA0010 |
| 4. Detection | 1-2 days | SIEM/EDR coverage gap | TA0042 Resource Development (defensive) |
| 5. Report | 2-3 days | Finding 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: 8hKickoff Meeting Agenda (1 hour)
- Scope review + signoff (10 min)
- ROE walkthrough + restrictions (15 min)
- Communication channel + escalation (10 min)
- Asset inventory hand-off (15 min)
- Q&A + first-day planning (10 min)
Closeout Meeting Agenda (1.5 hours)
- Executive summary (10 min)
- Top 3 critical finding walkthrough (30 min)
- Remediation roadmap (20 min)
- Detection rule hand-off (15 min)
- 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.mdOut-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.
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
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.

