Security reconnaissance. USE WHEN recon, reconnaissance, bug bounty, attack surface. SkillSearch('recon') for docs.
Customization
Before executing, check for user customizations at:~/.claude/skills/PAI/USER/SKILLCUSTOMIZATIONS/Recon/
If this directory exists, load and apply any PREFERENCES.md, configurations, or resources found there. These override default behavior. If the directory does not exist, proceed with skill defaults.
recon
Infrastructure and Network Reconnaissance
🚨 MANDATORY: Voice Notification (REQUIRED BEFORE ANY ACTION)
You MUST send this notification BEFORE doing anything else when this skill is invoked.
Send voice notification:
curl -s -X POST http://localhost:8888/notify \
-H "Content-Type: application/json" \
-d '{"message": "Running the WORKFLOWNAME workflow in the Recon skill to ACTION"}' \
> /dev/null 2>&1 &
Output text notification:
Running the **WorkflowName** workflow in the **Recon** skill to ACTION...
This is not optional. Execute this curl command immediately upon skill invocation.
Purpose
Technical reconnaissance of network infrastructure including domains, IP addresses, netblocks, and ASNs. Combines passive intelligence gathering with authorized active scanning to map attack surfaces and identify assets.
When to Use This Skill
Core Triggers - Use this skill when user says:
Direct Recon Requests
"do recon on [target]" or "run recon"
"perform reconnaissance on [target]" or "conduct recon"
"do infrastructure recon" or "network reconnaissance"
Work scratch/ (~/.claude/MEMORY/WORK/{current_work}/scratch/) - For iterative artifacts during investigation
MEMORY/RESEARCH/ (~/.claude/MEMORY/RESEARCH/YYYY-MM/) - For pentest engagements and formal assessments
MCP Profile Requirements
For passive recon: No special MCP profile needed
For active recon: Requires security MCP profile
# Switch to security profile
~/.claude/MCPs/swap-mcp security
# Restart Claude Code to apply# Then run active reconnaissance
Security profile includes:
httpx (HTTP probing)
naabu (port scanning)
Other security tools
Ethical and Legal Considerations
CRITICAL RULES:
Authorization First - Never perform active scanning without explicit authorization
Scope Validation - Ensure targets are in-scope for testing
Rate Limiting - Respectful scanning, no DoS or aggressive techniques
Documentation - Log all recon activities with timestamps and authorization
Responsible Disclosure - If vulnerabilities found, follow responsible disclosure
No Destructive Testing - Reconnaissance only, no exploitation
Authorization Types:
Pentest engagement (written SOW/contract)
Bug bounty program (in-scope targets only)
Owned assets (your own infrastructure)
Research lab/CTF environments
Never scan:
Systems without permission
Out-of-scope targets
Critical infrastructure
Government systems (without specific authorization)
When in doubt: Ask for explicit confirmation and documented authorization.
Usage Examples
Example 1: Passive Domain Recon
User: "Do passive recon on example.com"
Assistant: Activating recon skill with passive-recon workflow.
Target: example.com
Mode: Passive only (no active scanning)
[Performs WHOIS, DNS, cert transparency, IPInfo]
[Generates report in scratchpad]
Report: ~/.claude/MEMORY/WORK/{current_work}/scratch/recon-example-com/
Example 2: IP Investigation with Active Scan
User: "Investigate IP 1.2.3.4 - I own this server"
Assistant: Activating recon skill with ip-recon workflow.
Target: 1.2.3.4
Authorization check: You confirmed this is an owned asset.
Proceeding with passive + active reconnaissance.
[Performs IPInfo, reverse DNS, WHOIS, port scan, service detection]
[Generates comprehensive report]
Report: Open ports found (22, 80, 443)
Services: SSH, HTTP, HTTPS
Technologies: nginx 1.20.1, OpenSSH 8.2
Example 3: Integration with OSINT
User: "Do OSINT on Acme Corp and map their infrastructure"
Assistant: Activating OSINT skill...
Found domains: acme.com, acmecorp.com, acme.io
Now calling recon for infrastructure mapping...
[Recon skill maps each domain]
[Discovers subdomains, IPs, netblocks]
[Creates comprehensive infrastructure map]
Report: Complete OSINT + Infrastructure report
15 domains, 47 subdomains, 3 netblocks identified