recon

Map a target's external attack surface and route candidates to vulnerability-class hunters.

1|Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework --skill recon-maybe4a6f7365
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recon
Source: https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework/tree/main/skills/recon
Command: npx skills add https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework --skill recon-maybe4a6f7365

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a bug-bounty engagement without a structured map of the target's attack surface leads to missed endpoints, out-of-scope probing, and unorganized findings. This Skill runs a directed reconnaissance pipeline that stays within program scope and produces a routed candidate surface instead of raw URL dumps. ## Core Features & Use Cases - JS-bundle-first mining: Extract hidden endpoints, routes, feature flags, and secret-shaped strings from source maps and webpack chunks before any brute enumeration. - Full enumeration pipeline: Subdomain discovery (subfinder/amass), live-host probing (httpx), JS-aware crawling (katana), historical URLs (gau/waybackurls), and parameter mining (Arjun), each with documented fallbacks. - Class-based routing: Bucket candidates with gf patterns and route each item to the matching CWE hunter (SSRF, XSS, SQLi, IDOR, path traversal, and more) as an observation, not a finding. - Use Case: At the start of an engagement against a new bug-bounty target, run this Skill to build a scoped surface map in notes/recon/surface-map.md and refresh pre_scan.yaml with unresolved candidates for the hunters. ## Quick Start Run the recon skill to map the attack surface of the current target and route the discovered endpoints to the appropriate vulnerability hunters.

Frequently Asked Questions about recon

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map a target's attack surface for bug bounty recon?

Start by mining JavaScript bundles and source maps for hidden endpoints, then run subdomain enumeration with subfinder, probe live hosts with httpx, crawl with katana, pull historical URLs with gau, and mine parameters with Arjun. Each step has documented fallbacks if a tool is unavailable.

What tools are used for subdomain enumeration and crawling?

Subdomain discovery uses subfinder with amass passive and assetfinder as fallbacks. Crawling uses katana with gospider or hakrawler as alternatives, and historical URLs come from gau or waybackurls.

How are recon results routed to vulnerability hunters?

Collected URLs are bucketed with gf patterns such as gf ssrf, gf xss, gf sqli, and gf lfi. Each bucket is routed to the matching CWE hunter skill as an observation, which must later be confirmed through dynamic PoC validation.

Does recon stay within bug bounty program scope?

Yes. The pipeline builds an in-scope allowlist from the program policy and contract.yaml before any request, throttles to 1-2 requests per second with no concurrency, and never probes hosts that fail the allowlist check. Public reachability is explicitly not treated as permission.

What are the limitations of recon output?

Recon produces a candidate surface, not findings. Discovered endpoints are observations that carry no vulnerability claim until a hunter and dynamic PoC validation confirm them, and URL volume is explicitly not a success metric.