recon
Skill4 starsChanged 8 months agoMITView on GitHub
Recon workflow for domain, DNS, host, and web surface mapping.
27 other projects use a version of this.
Adopted by
Most recently taken up by
- trebaud/skillstheir own version, first seen Nov 8, 2026
- venhdev/skillstheir own version, first seen Nov 8, 2026
- lohi-ai/babysittheir own version, first seen Nov 8, 2026
- LeonardiFranco/skillstheir own version, first seen Nov 8, 2026
- blamechris/chroxytheir own version, first seen Nov 8, 2026
- g-baskin/recontheir own version, first seen Nov 8, 2026
Used with
Projects with it also use osint, web-pentest and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JosBen74Skillosint
OSINT-sökning och informationsinhämtning från öppna källor för Länsstyrelsen VG
Also in 4 projects that use this
samklee1Skillweb-pentest
Orchestrates authorized web app pentesting on Kali Linux using Opus sub-agents with difficulty-aware planning (TDA/EGATS), browser-first exploration, iterative verification, two-layer review (per-sub-agent + phase-level), optional cross-model gap audit (GPT/codex via codex-plugin-cc), and enforced KB updates. Trigger on: pentesting, penetration testing, web app security assessment, vulnerability assessment, OWASP testing, PTES, attack surface mapping, API security testing, pentest reporting, or 'help me test this app'. NOT for network-only pentesting, malware analysis, reverse engineering, or CTFs.
Also in 3 projects that use this
SentrySkillcreate-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
Also in 3 projects that use this
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- codexstar69/bug-hunter★ 546same name
- briiirussell/cybersecurity-skills★ 489same name
- gavraz/recon★ 263same name
- skyf0xx/gambit★ 29same name
- wycats/ai-plugin★ 19same name
- wycats/vscode-ai-plugin★ 19same name
- sophonfinance-wq/finance-automation-portfolio★ 16same name
- blamechris/chroxy★ 8same name
- g-baskin/recon★ 8same name
- franco-bianco/claude-skills★ 4same name
17 more not listed
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 repository8 other files it gives its agents.
- bug-huntingSkill
- exploitationSkill
- pentest-toolsSkill
- planningSkill
- reportingSkill
- research-notesSkill
- traffic-proxySkill
- xray-suiteSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 22 edited versions we read keep these.
1
Distinctive
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 48
Stop broad discovery when either condition is true:
“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
recon
Workflow
- Subdomain discovery
- subfinder -d
<domain> - amass enum -d
<domain>
- DNS mapping
- dnsenum
<domain> - theHarvester -d
<domain>-b all
- Service discovery
- nmap -sV -Pn
<target>
- Web fingerprinting
- httpx
<target> - whatweb
<target> - wafw00f
<target>
- Content discovery
- ffuf/gobuster/dirsearch
- katana for URL crawl
Exit criteria
- Live hosts list, open ports, tech stack, WAF status, and high-value endpoints recorded.
High-yield endpoint map strategy
Collect endpoints from three sources and merge:
- Live probing and crawl (httpx/katana)
- Historical archives (gau/waybackurls)
- Parameter discovery (arjun)
Tag endpoints quickly by risk:
- auth-critical: login, reset, token, oauth, session
- object-critical: /user/, /account/, /invoice/, /order/, /api/v*/id
- admin/internal: /admin, /internal, /debug, /graphql
Recon stop condition
Stop broad discovery when either condition is true:
- 20+ high-value unique endpoints are mapped, or
- Two consecutive recon runs produce only duplicates.
Then switch to verification-focused testing.
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.