openapi-devtools-scan

Extract API endpoints and secrets from a running web application via Chrome DevTools MCP.

9|2|Updated Jul 15, 2026
One-click install
npx skills add https://github.com/IgorSasovets/devsecops-with-claude --skill openapi-devtools-scan-igorsasovets
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openapi-devtools-scan
Source: https://github.com/IgorSasovets/devsecops-with-claude/tree/main/openapi-spec-creator/.claude/skills/OPENAPI_DEVTOOLS_SCAN
Command: npx skills add https://github.com/IgorSasovets/devsecops-with-claude --skill openapi-devtools-scan-igorsasovets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chrome-devtools-mcp.

What problem does it solve? When you have access to a running web application but not its source code, discovering its API surface for OpenAPI spec generation is difficult. This Skill inspects the live app through Chrome DevTools MCP to extract endpoints from loaded JavaScript bundles and network traffic, producing structured recon artifacts for downstream spec building. ## Core Features & Use Cases - JS Bundle Endpoint Extraction: Enumerates loaded scripts, skips vendor bundles, and runs targeted regex passes over app bundles to find fetch, axios, XHR, and route constant patterns. - Secrets Detection: Scans frontend JavaScript for TruffleHog-style patterns (AWS keys, GitHub tokens, JWTs, private keys) and records only redacted previews with file offsets. - Optional Network Capture and Authentication: Authenticates via form, token, or cookie, then navigates the app to capture XHR/fetch traffic for higher endpoint coverage. - Use Case: A security engineer points the Skill at https://app.example.com with credentials, and receives routes.json, LIVE_RECON.md, and a redacted secrets report ready to feed into an OpenAPI spec builder. ## Quick Start Scan the live application at https://app.example.com for API endpoints and secrets, using authenticated access and network capture.

Frequently Asked Questions about openapi-devtools-scan

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

FAQPage Schema
How do I extract API endpoints from a running web application?▼

Connect Chrome DevTools MCP, then run the scan against the target URL. It enumerates loaded JavaScript bundles, applies regex patterns for fetch, axios, and XHR calls, and optionally captures network traffic to build a routes.json inventory.

How to detect secrets in frontend JavaScript bundles?▼

The scan runs TruffleHog-style regex patterns over app bundles to find AWS keys, GitHub tokens, JWTs, Stripe keys, and private key blocks. Findings record only the bundle URL, character offset, and a redacted preview, never the secret value itself.

What is the difference between live app scanning and source code recon?▼

Live scanning inspects what the application actually loads in production via the browser, while source recon analyzes the codebase directly. Live scanning cannot determine request/response parameter shapes, so source recon is recommended to enrich schemas.

Does the scan support authenticated applications?▼

Yes, it supports form-based login, Bearer token or API key headers, and cookie injection. Credentials are held in memory only and never written to any output file or captured in screenshots.

What are the limitations of live application API scanning?▼

Vendor bundles are skipped, navigation is capped at 10 actions, and parameter schemas cannot be inferred from live traffic. Low-confidence routes found only as path strings should be validated manually or via source recon.