attack-surface
Skill37 starsChanged 5 months agoMITView on GitHub
Maps every entry point, component, and trust boundary of a target before testing begins prevents missed coverage and prioritizes the highest-value attack paths. Trigger when the user provides a target and wants to know where to start, says "map the attack surface", "what should I test", or "where do I begin", or is starting any engagement after scope-grill is complete.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- kirillgreen/skillstheir own version, first seen Sep 9, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- kirillgreen/skills★ 23same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository38 other files it gives its agents.
- ad-breachSkill
- ai-llm-hunterSkill
- bugbounty-reporterSkill
- cavemanSkill
- check-exploitSkill
- clickjacking-hunterSkill
- compliance-gap-analyzerSkill
- control-lookupSkill
- ctf-writeupSkill
- cvss-scorerSkill
- deadangleSkill
- droid-reconSkill
- economist-attackSkill
- engagement-handoffSkill
- finding-writerSkill
- find-skillsSkill
- graphql-raiderSkill
- hexstrike-forgeSkill
- high-severity-hunterSkill
- hpp-hunterSkill
- idor-hunterSkill
- js-analyzerSkill
- jwt-crackerSkill
- less-aggressive-attackSkill
- less-noise-attackSkill
- nuclei-template-writerSkill
- pentest-reportSkill
- redirect-forgeSkill
- redmindSkill
- remediation-plannerSkill
- risk-assessorSkill
- scope-grillSkill
- skill-benchmarkSkill
- ssrf-hunterSkill
- ssti-hunterSkill
- vuln-diagnoseSkill
- xss-hunterSkill
- xxe-phantomSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Before testing individual vulnerabilities, map the full attack surface.
- Distinctive: line 58
Follow with a Recommended Testing Order — ordered list of highest-value targets first.
- Distinctive: line 62
Do not start testing until Phase 1 is complete — partial maps lead to missed coverage
- Distinctive: line 63
If the scope is large, timebox Phase 1 and note what was not mapped
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Attack Surface Mapper
Before testing individual vulnerabilities, map the full attack surface. Untested components are unfound vulnerabilities. This skill produces a structured map that drives testing coverage.
Process
Phase 1 — Enumerate Entry Points
Systematically identify every place an attacker could interact with the target:
- Web — domains, subdomains, ports 80/443, login pages, API endpoints, file upload, search, export
- APIs — REST, GraphQL, SOAP, WebSocket, mobile API backends
- Auth flows — login, registration, password reset, OAuth/SSO, MFA bypass paths
- Network — open ports, admin interfaces (SSH, RDP, Telnet), VPNs, exposed management panels
- Cloud — S3 buckets, blob storage, exposed functions/lambdas, public AMIs, metadata endpoints
- Third-party integrations — webhooks, OAuth providers, embedded iframes, CDN-served content
- Client-side — JavaScript source, local storage, service workers, postMessage handlers
Phase 2 — Identify Trust Boundaries
Mark where the system transitions between trust levels:
- Unauthenticated → authenticated
- User role → admin role
- External network → internal network
- Client-controlled input → server-side processing
Phase 3 — Tech Stack Fingerprint
For each component, note:
- Language / framework
- Version (if visible)
- Authentication mechanism
- Known CVEs for the version (run
check-exploitskill on identified versions)
Phase 4 — Prioritize
Rank attack paths by value. See references/priority-matrix.md.
Output Format
Produce a Surface Map table:
| Component | Type | Auth Required | Tech Stack | Priority | Notes |
/api/v2/users | REST API | Bearer token | Node.js/Express | High | Returns PII |
admin.target.com | Web app | Basic auth | Apache/PHP | Critical | Exposed to internet |
Follow with a Recommended Testing Order — ordered list of highest-value targets first.
Rules
- Do not start testing until Phase 1 is complete — partial maps lead to missed coverage
- If the scope is large, timebox Phase 1 and note what was not mapped
- Reference
check-exploitfor every identified technology version
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.