Surface a one-page pentest cheatsheet for fast field recall. Use when the user asks for a "quick command", "cheatsheet", "one-liner", "what's the syntax for X", "remind me how to do Y", "give me the recon snippets", "AD cheatsheet", "lateral-movement one-liners", "AWS quick commands", "Azure quick commands", "mobile cheatsheet", "initial access cheatsheet", or any request that wants tools/commands without methodology overhead.
Installation
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Surface a one-page pentest cheatsheet for fast field recall. Use when the user asks for a "quick command", "cheatsheet", "one-liner", "what's the syntax for X", "remind me how to do Y", "give me the recon snippets", "AD cheatsheet", "lateral-movement one-liners", "AWS quick commands", "Azure quick commands", "mobile cheatsheet", "initial access cheatsheet", or any request that wants tools/commands without methodology overhead.
Pentest Cheatsheet Quick Recall
Pull the relevant one-page cheatsheet from the pentest-templates library and surface the matching snippet.
Library root
$PENTEST_LIBRARY — caminho absoluto deste repositório clonado (definido pelo instalador; veja INSTALL.md).
Available cheatsheets
Topic
File
Recon (passive + active)
cheatsheets/recon.md
Web app + API
cheatsheets/web-api.md
Active Directory
cheatsheets/active-directory.md
Lateral movement (Win/Linux)
cheatsheets/lateral-movement.md
AWS
cheatsheets/cloud-aws.md
Azure / Entra ID
cheatsheets/cloud-azure.md
Mobile (Android + iOS)
cheatsheets/mobile.md
Initial access (phishing infra)
cheatsheets/initial-access.md
How to operate
Map the user's request to one or more cheatsheet files above. Disambiguate with one short question only when truly ambiguous.
Read the file and surface the matching section. Quote commands verbatim — do not paraphrase. Preserve ⚠ (destructive), 🛰 (passive), 🎯 (post-ex) markers.
If the user asks for "one-liner X" and the cheatsheet doesn't have it, escalate to the relevant phase file (e.g., 04-infra-internal/05-credential-access.md) and pull the How to test block — but say so explicitly.
Always keep responses tight — the user wants the snippet, not the methodology. The associated pentest-* skill is where they go for depth.
When NOT to use
User wants methodology / why / acceptance criteria → use the type-specific pentest-* skill.
