recon
Skill1 starsChanged 3 months agoMITView on GitHub
This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.
32 other projects use a version of this.
Adopted by
Most recently taken up by
- brennantim/claude-skillstheir own version, first seen Nov 16, 2026
- moiz-73/glassboxtheir own version, first seen Nov 16, 2026
- Sn4kyGit/qa-agent-blueprinttheir own version, first seen Nov 16, 2026
- Birdiz/skillstheir own version, first seen Nov 16, 2026
- rafaym1/scholarship-desktheir own version, first seen Nov 16, 2026
- lohi-ai/babysittheir own version, first seen Nov 14, 2026
Used with
Projects with it also use web-pentest, create-pr and 1 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.
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 versions32 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 32
- 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
- rafaym1/scholarship-desk★ 18same name
- sophonfinance-wq/finance-automation-portfolio★ 16same name
- blamechris/chroxy★ 8same name
- g-baskin/recon★ 8same name
22 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 repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- agent-safetySkill
- ai-llmSkill
- apiSkill
- asset-graphSkill
- authSkill
- auto-researchSkill
- binary-analysisSkill
- business-logicSkill
- campaignSkill
- cicd-securitySkill
- cloudSkill
- cors-csrfSkill
- coverageSkill
- cross-accountSkill
- domain-modelSkill
- enrichmentSkill
- evaluation-harnessSkill
- file-uploadSkill
- graphql-auditSkill
- http-protocolSkill
- identity-domainSkill
- impact-verifierSkill
- meme-coin-auditSkill
- mobileSkill
- modern-browserSkill
- nuclei-scannerSkill
- oob-infraSkill
- osintSkill
- personaSkill
- plannerSkill
- privescSkill
- program-memorySkill
- race-conditionSkill
- rceSkill
- reportingSkill
- sastSkill
- scope-managerSkill
- skill-scientistSkill
- sqliSkill
- ssrfSkill
- standard-catalogSkill
- technique-kbSkill
- traffic-corpusSkill
- triage-validationSkill
- vuln-intelSkill
- web3-auditSkill
- xssSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Start with passive-subdomains unless prior evidence points to a more specific workflow.
- Very specific: line 17
Follow each workflow next mapping in skill.yaml after reviewing generated findings.
- Distinctive: line 18
If a workflow has no script reference, treat it as a manual or tool-native workflow and use the closest phase runbook when available.
“Common” is measured: kept by at least 6 in 10 of the 27 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
Overview
Full-stack reconnaissance for bug bounty targets — subdomains, DNS, ports, tech, crawling, URLs, JS, and asset inventory
This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.
Quick Reference
- Skill:
recon - Severity range:
info,low,medium - Required tools:
subfinder,amass,httpx,katana,gau,waybackurls,dnsx,naabu,nmap,wafw00f,openssl,jq,curl,python3 - Expected input files:
all_unique.txt - Scope check: confirm authorization before running intrusive or authenticated testing.
Workflow Selection
- Start with
passive-subdomainsunless prior evidence points to a more specific workflow. - Follow each workflow
nextmapping inskill.yamlafter reviewing generated findings. - If a workflow has no script reference, treat it as a manual or tool-native workflow and use the closest phase runbook when available.
- Runbooks: use
runbooks/and select the closest phase runbook when workflow names do not map 1:1.
Available Workflows
| Workflow | Purpose | Script paths | Primary outputs | Evidence |
passive-subdomains | Enumerate passive subdomains for a target domain. | .claude/skills/recon/scripts/subdomain_enum.py | $OUTDIR/recon/subdomains/subs.txt<br>$OUTDIR/recon/subdomains/findings.jsonl | $OUTDIR/recon/subdomains/evidence/ |
ct-index-enum | Fast CT-index enumeration (crt.name) with first-seen dates; set CT_NEW_DAYS=N to also emit newly observed assets to new_assets.txt. Sub-second responses vs crt.sh's frequent 502s. Free tier: 1000 req/day/IP. | .claude/skills/recon/scripts/ct_index_enum.py | $OUTDIR/recon/ctindex/subs_ctindex.txt<br>$OUTDIR/recon/ctindex/new_assets.txt (with CT_NEW_DAYS) | $OUTDIR/recon/ctindex/evidence/ |
live-discovery | Probe enumerated subdomains for live HTTP services. | .claude/skills/recon/scripts/live_discovery.py | $OUTDIR/recon/live/live_hosts.txt<br>$OUTDIR/recon/live/live_full.csv<br>$OUTDIR/recon/live/findings.jsonl | $OUTDIR/recon/live/evidence/ |
js-recon | Extract JavaScript URLs, download bundles, and scan for endpoints or secrets. | .claude/skills/recon/scripts/js_recon.py | $OUTDIR/recon/js/js_files.txt<br>$OUTDIR/recon/js/js_secrets.txt<br>$OUTDIR/recon/js/js_endpoints.txt<br>$OUTDIR/recon/js/findings.jsonl | $OUTDIR/recon/js/evidence/ |
Evidence Required
- Save raw request and response data for each confirmed finding.
- Include timestamps, affected target, exact workflow name, tool versions, and reproduction steps.
- Store screenshots or terminal captures in the workflow evidence directory when the workflow defines one.
- Evidence templates from
skill.yaml: takeover_candidate: DNS CNAME chain + HTTP probe + screenshotopen_admin_panel: Full curl with headers + screenshot + timestampzone_transfer: Full AXFR dump with NS server info and timestamp
References
- Source of truth:
skill.yaml - Runbooks:
runbooks/ - OWASP WSTG:
WSTG-INFO-01,WSTG-INFO-02,WSTG-INFO-03,WSTG-INFO-04,WSTG-INFO-05,WSTG-INFO-06,WSTG-INFO-07,WSTG-INFO-08,WSTG-INFO-09,WSTG-INFO-10
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.

