web2-recon

Builds evidence-gated host, path, and API attack-surface maps for authorized web reconnaissance.

10|3|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill web2-recon-baiqigo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web2-recon
Source: https://github.com/baiqigo/baiqi-redteam-lab/tree/main/.agents/skills/web2-recon
Command: npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill web2-recon-baiqigo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Authorized black-box web and API assessments often produce noisy, unverifiable asset lists that mix out-of-scope hosts, stale DNS records, and false positives. This Skill enforces an evidence-gated workflow that turns raw discovery signals into a scoped, attributable attack-surface map with provenance, ownership, status, tech stack, and labels. ## Core Features & Use Cases - Engagement Gating: Requires declared authorization, locked scope, and host/identity/path baselines before any probing begins. - Minimal Safe Validation: Orders checks from low-cost to higher-cost: host availability, soft-404 baseline, homepage/robots/security contacts, browser network capture, then JS/API surface enumeration. - False-Positive Oracles: Treats WAF blocks, captchas, timeouts, and scanner hits as INCONCLUSIVE, and rejects assets lacking reproducible sourcing or current reachability. - Use Case: During an authorized bug-bounty engagement, feed newly discovered in-scope hosts into the workflow to produce a validated asset graph, then route JS/API findings to SPA analysis and stack/CVE findings to vulnerability methodology skills. ## Quick Start Use web2-recon to build an evidence-gated asset map for my authorized in-scope web targets starting from the declared scope baseline.

Frequently Asked Questions about web2-recon

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

FAQPage Schema
How do I validate discovered web assets before adding them to scope?

Validate each asset by confirming a reproducible discovery source, current reachability, an explicit scope decision, and at least one HTTP or browser evidence artifact. DNS resolution or open ports without ownership attribution do not qualify as valid assets.

What is a soft-404 baseline in web reconnaissance?

A soft-404 baseline captures how a target responds to non-existent paths so later probes can distinguish real content from generic error pages. Establishing it before path enumeration prevents false positives when mapping hosts and APIs.

Can FOFA or search engine results be used directly as scan targets?

No. FOFA, ARL, Kali tooling, and search results only produce candidate assets. Each candidate must pass an individual scope check and ownership verification before any probing is permitted.

When should web reconnaissance stop during an engagement?

Stop when encountering cross-organization subdomains, CDN or back-end infrastructure outside scope, third-party SaaS, or any unapproved full-port or directory brute-forcing. Irreversible side effects or shared-user data also trigger immediate stops.

How are WAF blocks and captchas handled during probing?

WAF responses, captchas, timeouts, single errors, and scanner hits are all classified as INCONCLUSIVE rather than success or failure. They cannot serve as evidence for or against an asset's validity.