Individual skill
attack-surface-inventory
Structured normalization of discovered attack surface into the Endpoint Inventory note for downstream planning
internal/tools/skills/data/reconnaissance/attack-surface-inventory/SKILL.md
Source commit d42f381ad34843e71a42658e5c57290c713e85af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,323
- Repository last updated
- Nov 8, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- cybersecurity Repository topic
- security Repository topic
- bug-bounty Repository topic
- automation Repository topic
- autonomous-pentesting Repository topic
- ai-agent Repository topic
- ai-security Repository topic
- ethical-hacking Repository topic
- golang Repository topic
- penetration-testing Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,735 bytes
Read excerpt
# Attack Surface Inventory
## When to Use
After crawling, content discovery, JS analysis, and API discovery, normalize all findings into a structured inventory that the planner and specialist lanes can consume.
## Format
Save an `add_note` with key "Endpoint Inventory" using this structure:
```
GET / - main page
GET /login - login form
POST /login - form action (params: username,password)
GET /api/users - API endpoint (params: ?id, ?page)