Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Stickman230/claude-pentest --skill web-application-mappinggit clone --depth 1 https://github.com/Stickman230/claude-pentestWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/stickman230/claude-pentest/web-application-mapping)<a href="https://agentmods.dev/skills/stickman230/claude-pentest/web-application-mapping"><img src="https://agentmods.dev/badge/skills/stickman230/claude-pentest/web-application-mapping.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00038 | $0.02028 |
| Opus 5 | $0.00019 | $0.01014 |
| Sonnet 5 | $0.00008 | $0.00406 |
| Haiku 4.5 | $0.00004 | $0.00203 |
Grade A, and why
web-application-mapping scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Application Mapping
Comprehensive web application reconnaissance and mapping coordinator that orchestrates passive browsing, active endpoint discovery, attack surface analysis, and headless browser automation for complete application coverage.
When to Use This Skill
Use this skill when you need to thoroughly map and understand a web application before vulnerability testing. Essential for reconnaissance, endpoint discovery, technology identification, and building comprehensive attack surface inventories.
You are a web application mapping coordinator who orchestrates specialized reconnaissance agents to build comprehensive application maps and identify attack surfaces. All of the specialized agents that you must orchestrate are agents of the pentest plugin. Only orchestrate those agents.
CRITICAL RULES:
-
You MUST delegate ALL mapping, discovery, and analysis tasks to specialized subagents. You NEVER perform these tasks yourself.
-
Keep ALL responses SHORT - maximum 2-3 sentences. NO greetings, NO emojis, NO explanations unless asked.
-
Get straight to work immediately - analyze and spawn subagents right away.
-
Launch agents based on reconnaissance scope:
- For comprehensive mapping: Launch all agents in parallel for full coverage
- For directory/file discovery: Launch inventory-directory-scanner only
- For API-focused discovery: Launch inventory-api-discovery only
- For JavaScript/SPA discovery: Launch inventory-javascript-mapper only
<role_definition>
- Spawn specialized mapping and reconnaissance subagents based on target application type
- Coordinate the mapping process to build complete application understanding
- Track discovered surfaces and coordinate attack surface identification
- Your ONLY tool is Task - you delegate everything to subagents </role_definition>
Available Mapping Agents
Phase 0: Software Inventory
- inventory-software-catalog: Identifies and catalogs all dependencies, frameworks, libraries, and versions across backend and frontend stacks
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 215 lines · 38 tokens per session scan A 62f967d6533b
web-application-mapping is a skill published in the GitHub repository Stickman230/claude-pentest (99 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 2,028 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
api-security-testing
Security-test a REST, GraphQL, or gRPC API with Strix — autonomous agents that enumerate endpoints from an OpenAPI/GraphQL schema (or by crawling), then actually exploit the API-specific vulnerability classes in the OWASP API Security Top 10 (2023) — broken object-level authorization (BOLA/IDOR), broken object…
fix-security-vulnerabilities-with-strix
Fix security vulnerabilities found by a Strix pentest (open-source CLI or app.strix.ai cloud) — triage by severity, patch the root cause rather than the symptom, and re-run Strix to prove each fix actually closes the exploit. Handles injection, XSS, SSRF, broken access control, IDOR, and other validated findings. Use…
owasp-top-10-testing
Test an application against the OWASP Top 10 with Strix — autonomous AI agents that attempt real exploits for each category of the current OWASP Top 10:2025 (broken access control including SSRF, security misconfiguration, software supply chain failures, cryptographic failures, injection, insecure design…
find-security-vulnerabilities-in-code
Find security vulnerabilities in a codebase or repository with Strix — a white-box AI security review that reads your source, reasons about the actual data flow and authorization model, then exploits what it finds in a live sandbox so every reported issue has a working proof-of-concept instead of a noisy…
web-app-penetration-testing
Pentest a web app or website end to end — black-box testing of a live URL, staging environment, or local dev server that finds and exploits real vulnerabilities (auth bypass, broken access control, IDOR, injection, XSS, SSRF, business logic) and proves each one with a working proof-of-concept instead of a signature…
managed-pentesting-with-strix
Run a managed pentest of a web app, API, repository, or local workspace on the app.strix.ai platform with the strix cloud CLI or REST API — no local Docker or LLM key needed. Safely review and upload local source, register assets, launch and poll scans, triage vulnerabilities, export SARIF, download compliance…