recon-js-endpoints

Normalize, deduplicate, and categorize API endpoints from JavaScript files.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/salmanabdurrahman/pi-pentest-agent --skill recon-js-endpoints
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recon-js-endpoints
Source: https://github.com/salmanabdurrahman/pi-pentest-agent/tree/main/skills/recon-js-endpoints
Command: npx skills add https://github.com/salmanabdurrahman/pi-pentest-agent --skill recon-js-endpoints

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of noisy, unorganized, and potentially out-of-scope API endpoints extracted from JavaScript files, which often contain duplicates, relative paths, and template literals that are difficult to test manually.

Core Features & Use Cases

  • Endpoint Normalization: Automatically converts raw URL patterns into canonical forms by handling relative paths, query parameters, and dynamic variables.
  • Intelligent Categorization: Maps discovered endpoints to specific vulnerability categories like IDOR, SSRF, or Authentication, ensuring they are routed to the correct testing workflow.
  • Use Case: During a web application assessment, use this skill to process thousands of endpoints found in client-side JS, deduplicate them, and prioritize high-risk admin or IDOR-prone routes for further security validation.

Quick Start

Use the recon-js-endpoints skill to normalize and categorize the raw endpoint list extracted from the target JavaScript files.

Frequently Asked Questions about recon-js-endpoints

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

FAQPage Schema
How do I normalize and deduplicate API endpoints extracted from JavaScript files?

To normalize and deduplicate API endpoints extracted from JavaScript files, process the raw URL patterns through canonical conversion to handle relative paths, query parameters, and template literals, resulting in a clean, structured inventory for testing.

What is the best way to categorize JavaScript API routes for vulnerability testing?

Categorizing JavaScript API routes for vulnerability testing involves mapping normalized endpoints to specific security categories like IDOR, SSRF, or Authentication, ensuring high-risk routes are prioritized for the correct testing workflow.

How do I prepare raw JavaScript endpoints for attack surface mapping?

Preparing raw JavaScript endpoints for attack surface mapping requires filtering in-scope targets and deduplicating noisy paths to generate a structured inventory safe for non-malicious endpoint probing.

Can I use endpoint normalization to handle template literals and relative paths during web reconnaissance?

Endpoint normalization handles template literals and relative paths during web reconnaissance by automatically converting raw URL patterns into canonical forms, resolving duplicates and dynamic variables for accurate security testing.

Why do extracted JavaScript API routes contain duplicates and how do I filter them?

Extracted JavaScript API routes contain duplicates and noisy paths due to relative references and template literals; you filter them by applying normalization and deduplication to isolate in-scope targets and identify vulnerability candidates.

Does processing client-side JS endpoints work for prioritizing high-risk admin routes?

Processing client-side JS endpoints works for prioritizing high-risk admin routes by deduplicating the discovered paths and intelligently categorizing them to highlight IDOR-prone targets for further security validation.