recon-agent

Extracts API endpoints, request signatures, and secrets from JavaScript during authorized reconnaissance.

2|1|Updated Aug 28, 2026
One-click install
npx skills add https://github.com/lycheer1126/xs-bigdan --skill recon-agent-lycheer1126
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recon-agent
Source: https://github.com/lycheer1126/xs-bigdan/tree/main/knowledge/agents/recon
Command: npx skills add https://github.com/lycheer1126/xs-bigdan --skill recon-agent-lycheer1126

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manual reconnaissance of modern web applications misses most of the real attack surface because SPA frontends lazy-load JavaScript chunks and hide API definitions behind client-side routing. This Skill automates deep JavaScript collection and analysis so that endpoint-to-parameter mappings, hardcoded credentials, and technology fingerprints are captured systematically instead of by ad-hoc browsing. ## Core Features & Use Cases - Dual-channel JS collection: Combines headless browser probing (browser_probe) with direct download of script tags and Wayback Machine historical JS, then reads every file to extract full request signatures (method, Content-Type, required/optional parameters, auth scheme). - Structured endpoint mapping: Produces _endpoint_params.json with completeness metadata (analysis_completeness ≥ 0.8, ≥3 endpoints) that gates progression to later testing phases. - Fingerprinting and CVE matching: Identifies frameworks, WAF/CDN vendors, and dependency versions, then maps them to known CVEs (Fastjson, Shiro, Log4j, Spring Actuator). - Source leak mining: Searches GitHub/Gitee organizations, commits, and issues for leaked credentials, with a defined workflow to re-inject found credentials after later phases complete. - Use Case: Given an authorized target URL, run the recon phase to download all JS bundles, click through SPA menus to trigger lazy chunks, and produce a complete API attack-surface map plus an initial leaked-value pool for downstream linkage testing. ## Quick Start Run the recon agent against the authorized target URL to collect all JavaScript files, extract API endpoints with their parameters, and generate the _endpoint_params.json attack-surface map.

Frequently Asked Questions about recon-agent

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

FAQPage Schema
How do I extract API endpoints from JavaScript files?

Download all JS files locally, then read each file completely to extract URLs plus HTTP method, Content-Type, required and optional parameters, and auth scheme. Record results in _endpoint_params.json with source file attribution for each endpoint.

How to find hidden APIs in SPA lazy-loaded chunks?

Click through every visible menu, tab, and pagination control in the rendered page while monitoring network requests for new script resources. Download each newly loaded chunk and analyze it, since lazy-loaded chunks frequently contain management interfaces and APIs.

What should I do when a WAF is detected during reconnaissance?

Switch to safe mode: send only single requests with 3-5 second delays between sensitive path probes, stop Swagger probing after the first 403, and limit admin path probing to a few requests per minute. Prefer passive JS analysis which carries no WAF trigger risk.

Does JS analysis work on traditional server-rendered sites?

Yes, via the fallback path: crawl pages to extract HTML forms with their action URLs, methods, and input names, then build the same _endpoint_params.json structure from form data. Value-pool linkage still applies to CSRF tokens and embedded variables.

Why does the recon phase gate reject my _endpoint_params.json?

The gate requires analysis_completeness of at least 0.8, at least 3 extracted endpoints, non-empty per-file analysis detail, and method plus source_files populated for every endpoint. Any missing condition blocks progression to the next phase.

How are leaked credentials from GitHub used in testing?

Credentials found in commits, config files, and issues are recorded in a credential list, then re-injected only after JS analysis and linkage testing complete. They are used for login attempts, JWT forgery, or cloud key takeover to escalate information leaks into full attack chains.