recon-planning

Orchestrates attack surface reconnaissance by splitting synchronous probing from asynchronous sub-agent enumeration.

632|86|Updated Apr 29, 2023
One-click install
npx skills add https://github.com/yaklang/yaklang --skill recon-planning-yaklang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: recon-planning
Source: https://github.com/yaklang/yaklang/tree/main/common/ai/aid/aireact/skills/recon-planning
Command: npx skills add https://github.com/yaklang/yaklang --skill recon-planning-yaklang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? During authorized penetration tests, reconnaissance often stalls: testers either wait idly for long scans (subdomain enumeration, port scanning, deep crawling) or get stuck on a single entry point while other live assets go untested. This Skill structures recon so short tasks run synchronously on the main thread while long-running expansion and deep-dive work is delegated to sub-agents, keeping continuous output of new entry points, leads, and conclusions. ## Core Features & Use Cases - Sync/Async Task Splitting: Immediate HTTP probing, baseline recording, and first-shot testing happen on the main line; subdomain discovery, port scanning, deep crawling, directory guessing, and history/repo mining are dispatched to sub-agents. - Asset Inventory & Todo Proliferation: Every asset is tracked with status (alive / dead / duplicate / pending / deep-diving), and sub-agent results are immediately converted into new todos rather than stored as passive logs. - Semantic-Guided First Shots: Parameters are mapped to test surfaces by meaning—IDs to authorization checks, URLs to server-side requests, filenames to file reads, templates to rendering probes—with baseline comparison required. - Use Case: Given a corporate domain as an authorized target, the Skill probes web entry points immediately, dispatches subdomain and certificate-SAN expansion to sub-agents, treats 401/403 login walls as live sites, and keeps expanding the test queue as new hosts, keys, and hidden routes flow back. ## Quick Start Perform attack surface reconnaissance on the authorized target example.com, probing live entry points now and delegating subdomain and port expansion to sub-agents.

Frequently Asked Questions about recon-planning

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

FAQPage Schema
How do I structure reconnaissance during an authorized penetration test?▼

Split work by duration: run quick HTTP probes, baseline recording, and first-shot tests synchronously, while delegating subdomain enumeration, port scanning, deep crawling, and history mining to asynchronous sub-agents. Convert every returned lead into new todos immediately.

What tasks should be delegated to sub-agents in attack surface mapping?▼

Delegate long-running work: DNS and subdomain enumeration, certificate SAN expansion, port scanning with fingerprinting, deep crawling, directory and backup guessing, historical snapshot review, JS bundle analysis, and public repository mining. Keep short request-response probes on the main line.

Should 401 or 403 responses be treated as dead targets?▼

No. 401, 403, login walls, and admin challenge pages indicate live sites and must stay in scope. Only unreachable hosts, timeouts, parked pages, or responses with no business content count as non-alive. A directory returning 403 does not mean individual files are absent.

How do I choose which injection or authorization tests to run first?▼

Map parameters by semantics: IDs and tenant fields to object-level authorization checks, filenames to file-read probes, URLs and callbacks to server-side request tests, search and filter fields to injection baselines, and template fields to harmless rendering probes. Always compare against a recorded baseline.

What are the limits of fingerprint and scanner results in recon?▼

Fingerprints, version banners, and scanner template hits are not confirmed vulnerabilities. High-severity findings come from systematic coverage and manual verification on the actual target, not from running full scanner templates as a substitute for testing.