web2-recon

Automate web2 reconnaissance to produce a prioritized asset list.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/venkatas/obsidian --skill web2-recon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web2-recon
Source: https://github.com/venkatas/obsidian/tree/main/skills/web2-recon
Command: npx skills add https://github.com/venkatas/obsidian --skill web2-recon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web2 reconnaissance often requires assembling data from many sources to map an attack surface. This skill automates subdomain enumeration, live host discovery, URL crawling, JS analysis, and continuous monitoring to produce a ready-to-hunt asset list.

Core Features & Use Cases

  • Subdomain enumeration using multiple sources (Chaos API, subfinder, assetfinder)
  • Live host discovery and HTTP analysis (dnsx, httpx)
  • URL crawling and historical URL collection (katana, waybackurls, gau)
  • JS analysis and continuous monitoring (LinkFinder, SecretFinder, new subdomain alerts, GitHub commit watch)
  • Use case: starting recon on new web2 targets or mapping attack surface for asset discovery.

Quick Start

Provide a target domain and run the web2-recon pipeline to generate a prioritized URL list ready for hunting.

Frequently Asked Questions about web2-recon

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

FAQPage Schema
How do I automate subdomain enumeration and web2 recon for a new target domain?

Automate web2 recon by running a pipeline that aggregates subdomain data from subfinder, Chaos API, and assetfinder. It maps exposure surfaces by discovering live hosts, crawling URLs, and analyzing JS files to produce a prioritized asset list for hunting.

What is the best way to map a web2 attack surface across multiple domains or subnets?

Mapping a web2 attack surface requires aggregating live hosts and URLs across domains, IPs, or subnets. This skill scales results from multiple sources using dnsx and httpx, outputting structured artifacts suitable for continuous monitoring and reporting.

How do I extract endpoints and secrets from JavaScript files during asset discovery?

Extract endpoints and secrets during asset discovery by integrating JS analysis tools like LinkFinder and SecretFinder. The pipeline analyzes crawled JavaScript files to identify hidden findings and incorporates them into the prioritized URL list.

Do I need to install external tools like katana and waybackurls to use this recon pipeline?

Yes, you need external tools installed. The pipeline requires integration with subfinder, Chaos API, assetfinder, dnsx, httpx, katana, waybackurls, gau, LinkFinder, and SecretFinder to aggregate subdomain data, live hosts, URLs, and JS findings.

Can I use this skill for continuous monitoring and threat surface mapping?

Yes, you can use this skill for continuous monitoring and threat surface mapping. It generates structured artifacts that support ongoing asset discovery, triggering new subdomain alerts and GitHub commit watches to track exposure changes over time.

How does URL crawling and historical URL collection work in web2 reconnaissance?

URL crawling and historical collection in web2 reconnaissance works by gathering paths using katana, waybackurls, and gau. These tools aggregate current and historical URLs, feeding them into the pipeline to build a comprehensive prioritized asset list.