# pentest-engagement-methodology

pentest-engagement-methodology runs an authorized penetration test stage by stage, from scope and engagement rules to the final write-up. Useful when permission is signed and nothing should be missed.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 356 installs
- Author: securityskills
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/securityskills/skills/tree/HEAD/pentest/methodology/pentest-engagement-methodology/SKILL.md
- Updated: 2026-08-26
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/pentest-engagement-methodology

## What it does

This skill sets the order of work for a permitted penetration test. Scope and engagement rules come first, then reconnaissance, vulnerability analysis, exploitation, post-exploitation and reporting. Every stage says what to gather and what to log, and the box type (black, grey or white) is agreed up front along with test windows and escalation paths.

The guardrails are strict on purpose. No written permission means no testing, each host and domain is checked against the scope document before anything is sent, and destructive actions are off the table. If a target is ambiguous, the agent asks instead of assuming. Deliverables include the test plan, an asset inventory, the findings report, a cleanup log and an agenda for the debrief.

Reports follow a fixed shape: a plain-language summary for stakeholders, then findings with CVSS severity, affected assets, reproduction steps and fixes. Scanner output alone is not evidence. Findings get verified by hand, and the skill ranks them by how exploitable they really are.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add securityskills/skills --skill pentest-engagement-methodology -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/pentest-engagement-methodology/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/pentest-engagement-methodology/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add securityskills/skills --skill pentest-engagement-methodology -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/pentest-engagement-methodology/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add securityskills/skills --skill pentest-engagement-methodology -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/pentest-engagement-methodology/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install securityskills/skills pentest/methodology/pentest-engagement-methodology
```

2. **Manually: put the files in place**
- File: `.github/skills/pentest-engagement-methodology/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add securityskills/skills --skill pentest-engagement-methodology -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/securityskills/skills --path pentest/methodology/pentest-engagement-methodology
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/pentest-engagement-methodology/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add securityskills/skills --skill pentest-engagement-methodology -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/securityskills/skills/tree/HEAD/pentest/methodology/pentest-engagement-methodology/SKILL.md

## When to use it
- Scope an engagement before a single packet goes out
- Build an asset inventory during reconnaissance
- Verify scanner findings by hand
- Keep an evidence trail for each exploit attempt
- Write the report with severity ratings and reproduction steps

## Example prompts
- Draft the test plan for this scope, including test windows and escalation contacts.
- Check these hosts against the scope document and flag anything ambiguous.
- Turn these notes into a findings report with CVSS severity and remediation advice.

## Similar
- [pentest-engagement](https://affpapa.org/en/nevibecode/skills/pentest-engagement.md) — skill · 157 installs
- [net-pentest](https://affpapa.org/en/nevibecode/skills/net-pentest.md) — skill · ★ 106 repo stars
- [pentest-toolkit-pro-html](https://affpapa.org/en/nevibecode/skills/pentest-toolkit-pro-html.md) — skill · 344 installs
- [redteam-mindset](https://affpapa.org/en/nevibecode/skills/redteam-mindset.md) — skill · ★ 16193 repo stars
- [claude-bughunter](https://affpapa.org/en/nevibecode/plugins/claude-bughunter.md) — plugin · ★ 16193 repo stars
- [pentest-agents-bug-bounty-framework](https://affpapa.org/en/nevibecode/skills/pentest-agents-bug-bounty-framework.md) — skill · 1300 installs

From the same set: [securityskills/skills](https://affpapa.org/en/nevibecode/by/securityskills/skills.md) — 21 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
