web-recon-simple

Inspect web applications to map API endpoints, exposed tokens, technologies, and related CVEs.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/yogiex/opencode-cyber-security-skills --skill web-recon-simple-yogiex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: web-recon-simple
Source: https://github.com/yogiex/opencode-cyber-security-skills/tree/main/skills/web-reconnaissance
Command: npx skills add https://github.com/yogiex/opencode-cyber-security-skills --skill web-recon-simple-yogiex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual web reconnaissance is often unstructured and easy to skip steps. This Skill provides a repeatable checklist for quickly profiling a web target using only browser DevTools and simple curl commands, so nothing important gets missed. ## Core Features & Use Cases - JavaScript Bundle Analysis: Scan chunk and bundle files in DevTools Sources to uncover hidden API endpoints, internal paths, and comments. - Network & Storage Inspection: Capture XHR/Fetch requests, headers, and check LocalStorage, SessionStorage, and cookies for exposed tokens or session data. - Technology Fingerprinting & CVE Lookup: Identify server, framework, and language from headers and HTML markers, then search NVD and the web for matching CVEs with CVSS scores. - Use Case: During an authorized security assessment, run this checklist against a target web app to produce a structured report listing technologies, discovered endpoints, exposed tokens, and relevant CVEs. ## Quick Start Run the web recon checklist on https://target.com and produce a summary report of technologies, endpoints, exposed tokens, and related CVEs.

Frequently Asked Questions about web-recon-simple

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

FAQPage Schema
How do I find hidden API endpoints in a web application?▼

Open DevTools Sources tab and scan JavaScript chunk or bundle files for strings like /api/, /v1/, or /graphql. Combine this with the Network tab filtered by XHR/Fetch to capture live endpoint requests and their methods.

How to check for exposed tokens in browser storage?▼

Open DevTools Application tab and inspect Local Storage, Session Storage, and Cookies for tokens or session IDs. You can also run console.log(localStorage) and console.log(document.cookie) in the console, noting HttpOnly cookies are not readable by JavaScript.

How do I identify what technology a website uses?▼

Check response headers like Server, X-Powered-By, and Set-Cookie for backend hints, and inspect HTML source for markers like __NEXT_DATA__ (Next.js) or __NUXT__ (Nuxt). The Wappalyzer browser extension automates this fingerprinting.

Does this recon skill include exploit code for found CVEs?▼

No, the skill only identifies and records CVE IDs, CVSS scores, and affected versions found via NVD or web search. It explicitly excludes exploit code or proof-of-concept material, limiting output to vulnerability identification.

What tools are needed to run this web reconnaissance workflow?▼

Only a browser with DevTools and curl for quick header and endpoint checks are required. Wappalyzer is suggested as an optional extension, and searchsploit can be used read-only to list CVEs.