Skip to main content
command CX Codex

recommend · 0xsteph — Claude Code command: route pentest tasks to the right agent

recommend turns a freeform pentest task into a routing decision: names one or two specialist agents and lists the next commands. Useful when you know the goal but not which agent to pick.

MIT ★ 2,482 updated 2026-10-06

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/recommend.md
Open on GitHub

What recommend does

The command reads a task description and classifies it by domain: recon, web, AD, cloud, mobile, wireless, social engineering, malware, RE, forensics, detection, planning, reporting, CTF. It then picks a primary agent from the catalog and at most one hand-off agent.

It restates scope, environment type and rules of engagement, or asks a single question if scope is missing. The output includes 3–5 runnable commands with placeholders such as nmap -sV --top-ports 1000 <target>, plus one sentence on a pitfall or pivot signal.

The Claude Code install path is .claude/commands/recommend.md. Requests for mass targeting, unauthorized DDoS or attacks on third parties are refused outright.

What it helps with

  • classify a pentest task by domain
  • pick the best agent plus one hand-off
  • produce 3–5 concrete next commands
  • ask for the missing scope
  • refuse out-of-scope requests

Example prompts for the agent

  • /recommend map the external perimeter and tell me what to run next
  • /recommend I have AD access and need a privilege escalation plan
  • /recommend route this SQL injection finding to the right agent

How to install recommend

Manually: put the files in place

.claude/commands/recommend.md

Call it with /recommend. For all projects use ~/.claude/commands/

Questions about recommend

How do I install recommend in Claude Code?

Place it at .claude/commands/recommend.md. Claude Code will expose it as the /recommend command.

What does recommend do?

It classifies a freeform pentest task, picks one or two agents from the pentest-ai-agents catalog, and gives commands for the next steps.

What happens with out-of-scope requests?

Mass targeting, unauthorized DDoS, and attacks on third parties are refused: the command stops instead of inventing authorization.

Source text

recommend.md · MIT
---
description: Recommend the right pentest-ai agent and concrete next steps for a freeform task description.
argument-hint: <freeform task description>
---

You are routing a pentesting task to the right specialist agent. The user's task is below.

User task:
$ARGUMENTS

Do this in order:

1. **Classify the task.** Identify the primary domain (recon, web, AD, cloud, mobile, wireless, social engineering, malware, RE, forensics, detection, planning, reporting, CTF) and any cross-cutting concerns.

2. **Pick the agent (or two).** From the catalog below, name the single best agent. If a second agent would meaningfully help, name it as a hand-off. Don't list more than two.

3. **State the assumed scope.** Restate the in-scope assets, environment type (lab, internal, external, bug bounty, CTF), and any rules of engagement constraints visible in the request. If scope is missing, ask one direct question to fill the gap.

4. **Give 3–5 concrete next commands.** Real CLI invocations with placeholders the user can fill (`<target>`, `<wordlist>`). Not methodology paragraphs. Not "consider running nmap" — just `nmap -sV --top-ports 1000 <target>`.

5. **Note one thing to watch for.** A common pitfall, OPSEC consideration, or pivot signal that's specific to this task. One sentence.

Agent catalog (for routing):

- engagement-planner — pentest scoping, ROE, MITRE-mapped phased plans
- recon-advisor — Nmap/Nessus/BloodHound output analysis, target prioritization (Tier 2)
- osint-collector — domain recon, email harvest, breach data, social profiling
- exploit-guide — methodology for AD/web/cloud/post-ex (advisory)
- privesc-advisor — Linux/Windows privilege escalation
- cloud-security — AWS/Azure/GCP, IAM escalation, container escape, serverless
- api-security — REST/GraphQL/WebSocket, JWT, OAuth, OWASP API Top 10
- mobile-pentester — Android/iOS, Frida, Objection, MASTG/MASVS
- wireless-pentester — WPA/WPA2/WPA3, evil twin, 802.1X, Bluetooth
- social-engineer — phishing strategy, pretexting, vishing methodology
- phishing-operator — Evilginx, GoPhish, dnstwist, live campaign tooling
- vuln-scanner — Nuclei, Nikto, Nmap NSE, RouterSploit (Tier 2)
- web-hunter — ffuf, gobuster, sqlmap, dalfox, Commix (Tier 2)
- credential-tester — Hydra, Hashcat, John, CrackMapExec, wordlist generation
- attack-planner — multi-step attack chain construction with stealth/impact scoring
- bug-bounty — HackerOne/Bugcrowd methodology, dedup, report writing
- ad-attacker — BloodHound, Impacket, NetExec, Certipy, Kerberos abuse (Tier 2)
- exploit-chainer — chain low-severity findings into full compromise (Tier 2)
- poc-validator — generate and safely run PoC scripts to eliminate false positives (Tier 2)
- payload-crafter — msfvenom, Donut, custom loaders, paired with detection content
- reverse-engineer — Ghidra, JadX, Radare2, Binwalk, static analysis workflows
- swarm-orchestrator — coordinates multiple agents in parallel
- bizlogic-hunter — price manipulation, race conditions, authorization flaws (Tier 2)
- cicd-redteam — GitHub Actions, GitLab CI, Jenkins pipeline security
- detection-engineer — Sigma, Splunk SPL, Elastic KQL, Sentinel KQL rules
- threat-modeler — STRIDE/DREAD, attack trees, data flow diagrams
- forensics-analyst — evidence acquisition, memory/disk forensics, timeline
- malware-analyst — triage, dynamic analysis, IOC extraction, YARA
- stig-analyst — DISA STIG, GPO remediation, keep-open justifications
- report-generator — pentest reports, executive summaries, CVSS, remediation
- ctf-solver — HackTheBox, TryHackMe, PicoCTF, web/pwn/rev/crypto/forensics

Output format:

```
**Primary agent**: <name>
**Hand-off to (if any)**: <name or "none">

**Assumed scope**: <one sentence>

**Next commands**:
1. <command>
2. <command>
3. <command>

**Watch for**: <one sentence>
```

If the user's task is out of scope (mass targeting, unauthorized DDoS, attacks on third parties), say so directly and refuse to route. Do not invent fake authorization context.

© 0xSteph · MIT · 0xSteph/pentest-ai-agents

Similar slash commands

All slash commands for Security →

recommend by other authors comes first.

recommend SuperClaude-Org The recommend command maps a user request to suitable SuperClaude commands. Use it when you need help choosing a workflow, persona, or flag. CX Codex +1 ★ 23,950repo stars find-security-vulnerabilities-in-code usestrix find-security-vulnerabilities-in-code is a Claude Code skill for white-box code security reviews that confirms each finding with a working proof-of-concept. CX Codex +1 17,400installs hack yaklang hack acts as the primary router and safety gate for authorized penetration testing, code auditing, and incident triage. Enforces scope boundaries and stops without verified permission. CX Codex +1 4,800installs csp-bypass-advanced yaklang csp-bypass-advanced — a skill for Claude Code, Codex, Cursor and three more platforms covering Content Security Policy bypass techniques. CX Codex +1 4,000installs shannon KeygraphHQ The skill wires up Shannon: it reads your source code, maps attack vectors and runs real exploits to prove a vulnerability exists. CX Codex +1 3,000installs Synmerco — Confidential Escrow for AI Agent Commerce joelasota Synmerco — Confidential Escrow for AI Agent Commerce is a Claude Code MCP server for agent-to-agent commerce with escrow, trust scores, and delivery proofs for confidential work products. CX Codex +1 3,239installs shannon-ai-pentester reason-machines The shannon-ai-pentester skill for Claude Code performs white-box penetration testing of web apps and APIs, reading source code, running live exploits, and reporting only reproducible findings. CX Codex +1 1,700installs

From the same set55

The whole set →
engagement-planner engagement-planner plans an authorized pentest phase by phase, tags each technique with a MITRE ATT&CK ID, and drafts a rules of engagement template. CX Codex ★ 2,482repo stars iot-pentester iot-pentester runs an authorized security assessment of an IoT device end to end: firmware, UART/JTAG, BLE and sub-GHz radio, companion app, cloud API. Looks for default credentials and weak update signing. CX Codex ★ 2,482repo stars traffic-analyzer traffic-analyzer inspects offline pcap and pcapng captures to spot cleartext credentials, carve files, and flag suspicious traffic patterns. CX Codex ★ 2,482repo stars password-auditor password-auditor reviews password policy and storage, checks breach exposure, and plans lockout-safe credential tests. It does not perform live cracking or spraying. CX Codex ★ 2,482repo stars lateral-movement Plans post-foothold lateral movement paths for authorized engagements. Maps credential reuse and remote execution methods directly to detection telemetry. CX Codex ★ 2,482repo stars crypto-analyzer The crypto-analyzer subagent reviews cryptographic use, from weak algorithms and key handling to TLS, password hashing, and JWT issues. Use it for code-focused security analysis. CX Codex ★ 2,482repo stars data-exfiltrator The data-exfiltrator subagent for Claude Code validates DLP filters and egress monitoring with synthetic data, simulating export channels and the detections they should trigger. CX Codex ★ 2,482repo stars persistence-planner persistence-planner plans persistence methods for authorized penetration tests and red team jobs. Pairs every technique with cleanup procedures and detection rules. CX Codex ★ 2,482repo stars

Project sponsors

Companies that keep this analytics open