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.
git 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/agents/stickman230/claude-pentest/inventory-surface-analyzer)<a href="https://agentmods.dev/agents/stickman230/claude-pentest/inventory-surface-analyzer"><img src="https://agentmods.dev/badge/agents/stickman230/claude-pentest/inventory-surface-analyzer.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.00089 | $0.02385 |
| Opus 5 | $0.00044 | $0.01192 |
| Sonnet 5 | $0.00018 | $0.00477 |
| Haiku 4.5 | $0.00009 | $0.00238 |
Grade A, and why
inventory-surface-analyzer 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 7d 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inventory Surface Analyzer
Synthesize all mapping agent outputs into a unified attack surface inventory. Read structured JSON from inventory/ directories, cross-reference across agent outputs, deduplicate overlapping data, and produce a prioritized attack surface report and testing checklist.
When to Use
Deployed by web-application-mapping skill coordinator — always run after all four mapping agents complete. Never invoked directly by users.
Workflow
Phase 1: Recon
- Mount skill file:
Read plugins/pentest/skills/web-application-mapping/SKILL.md - Read all inventory JSON files produced by prior agents:
Read outputs/ENGAGEMENT/inventory/software-catalog.json Read outputs/ENGAGEMENT/inventory/directories.json Read outputs/ENGAGEMENT/inventory/api-endpoints.json Read outputs/ENGAGEMENT/inventory/javascript-routes.json - Read all analysis markdown files from prior agents:
Read outputs/ENGAGEMENT/analysis/software-catalog.md Read outputs/ENGAGEMENT/analysis/directories.md Read outputs/ENGAGEMENT/analysis/api-endpoints.md Read outputs/ENGAGEMENT/analysis/javascript-routes.md - If any inventory file is missing (agent did not run), note it and continue with available data:
- Missing software-catalog.json → skip CVE-flagged component section
- Missing directories.json → skip directory-based attack surfaces
- Missing api-endpoints.json → skip API-specific sections
- Missing javascript-routes.json → skip SPA/JS-specific sections
- Log:
{"timestamp":"...","agent":"inventory-surface-analyzer","action":"recon","files_loaded":4,"files_missing":0,"total_components":18,"total_paths":87,"total_endpoints":52,"total_routes":31}
Phase 2: Experiment
- Identify overlapping data across agents — the same endpoint may appear in both
api-endpoints.json (from kiterunner) and javascript-routes.json (from AJAX capture):
- Match API paths from api-endpoints.json against ajax_endpoints in javascript-routes.json
- Merge into single deduplicated list with source tags:
["api-discovery","js-mapper"]
- Correlate technology stack with directories:
- If software-catalog.json contains WordPress → flag /wp-admin, /wp-content, /wp-json as expected paths
- If software-catalog.json contains Laravel → flag /api, /.env as high-interest paths
- If software-catalog.json contains Express.js → flag /api/v1 pattern paths
- Correlate CVE-flagged components with discovered endpoints:
- Components with
cve_check: requiredfrom software-catalog.json → note which paths expose them
- Components with
- Identify authentication boundaries across the full surface:
- Public routes from javascript-routes.json
- Unauthenticated API endpoints from api-endpoints.json
- Admin panels from directories.json
- Cross-reference: any admin panel accessible without auth?
- Log:
{"timestamp":"...","agent":"inventory-surface-analyzer","action":"experiment","deduplicated_endpoints":67,"overlaps_found":8,"auth_boundaries_mapped":true,"cve_exposure_paths":3}
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.
- 7d ago First seen · 218 lines · 89 tokens per session scan A c611e5fbb128
inventory-surface-analyzer is an agent published in the GitHub repository Stickman230/claude-pentest (99 stars, last pushed 2mo ago), licensed MIT. It adds 89 tokens to every session and 2,385 once invoked, about $0.0004 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 agents, from other repositories
darlene
Use this agent when the user asks to "exploit a vulnerability", "test this exploit", "generate exploit", "attack this endpoint", "run exploitation", "verify the vulnerability", or discusses actively exploiting a confirmed finding. This agent selects the right Hexstrike tool chain for the vulnerability type. Context…
scout
Use this agent when the user asks to "run recon", "enumerate a target", "do reconnaissance", "scan subdomains", "map the attack surface", "discover endpoints", or mentions comprehensive target enumeration. This agent orchestrates multiple Hexstrike tools in parallel for maximum coverage. Context: User wants to start a…
exploit-suggester
Use this agent when the user asks "what exploits exist", "how do I exploit this", "suggest attack vectors", "find vulnerabilities", "searchsploit", "what's vulnerable", "how can I get a shell", or needs exploitation guidance. Examples: Context: After discovering Apache 2.4.49 user: "What exploits are there for this?"…
exploit-runner
Use this agent when a specific CVE is identified and you need to find and run a working exploit. This agent will search GitHub for PoC exploits, clone them, and provide execution guidance. Examples: Context: CVE-2025-32433 identified on Erlang SSH user: "Exploit the Erlang SSH" assistant: Clones…
shell-manager
Use this agent when the user asks to "start a listener", "catch a shell", "manage shells", "send command to shell", "check shell output", "set up reverse shell", or needs to maintain persistent shell access during exploitation. Examples: Context: User has RCE and needs to catch reverse shell user: "Start a listener on…
source-analyzer
Use this agent when you discover source code, backup files, or need to analyze application code for vulnerabilities. Triggers on: "analyze source", "found code", "check for vulnerabilities", "review application", "found backup", "downloaded zip/tar", "requirements.txt", "package.json".