recon-osint
Skill2 starsChanged 48 days agoMITView on GitHub
Use at the start of any authorized red-team or pentest engagement to map the target's attack surface — passive OSINT (domains, subdomains, certs, DNS, ASN/IP ranges, leaked credentials, employees, tech stack) and active recon (port/service discovery, web asset enumeration). Produces a scoped attack-surface inventory feeding the domain-specific pentest skills. Authorized engagements only.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- NoorQureshi/ronintheir own version, first seen Oct 11, 2026
- NoorQureshi/SploitAgenttheir own version, first seen Oct 11, 2026
- NoorQureshi/security-skillstheir own version, first seen Oct 11, 2026
- hypnguyen1209/offensive-claudetheir own version, first seen Sep 21, 2026
- jessefmoore/offensive-claude-codetheir own version, first seen May 23, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- hypnguyen1209/offensive-claude★ 401same name
- NoorQureshi/security-skills★ 27same name
- NoorQureshi/ronin★ 26same name
- NoorQureshi/SploitAgent★ 26same name
- jessefmoore/offensive-claude-code★ 2same 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 repository25 other files it gives its agents.
- active-directory-pentestSkill
- agentic-ai-securitySkill
- api-secure-designSkill
- api-security-auditSkill
- cicd-supplychain-securitySkill
- cloud-pentestSkill
- container-k8s-pentestSkill
- detection-engineeringSkill
- entra-cloud-pentestSkill
- iot-embedded-pentestSkill
- llm-app-defenseSkill
- llm-redteamSkill
- mobile-pentestSkill
- network-device-pentestSkill
- network-pentestSkill
- post-exploitationSkill
- privilege-escalationSkill
- red-team-opsSkill
- report-writingSkill
- social-engineeringSkill
- source-code-reviewSkill
- threat-modelSkill
- vuln-chainingSkill
- web-app-pentestSkill
- wireless-pentestSkill
The file
Files
Reconnaissance & OSINT
The first phase of every engagement: understand the target's real attack surface before touching it hard. Passive recon leaves no footprint on the target; active recon interacts and must stay strictly in scope.
0. Authorization gate
- Written scope: in-scope domains, IP ranges/ASNs, cloud accounts, apps.
- Explicit out-of-scope assets and third parties (never recon a provider you aren't cleared for).
- Rules on active scanning (rate, hours, allowed tooling).
- OSINT-on-people rules (many programs restrict employee targeting).
1. Passive OSINT (no target interaction)
- Domains & subdomains: certificate transparency logs, passive DNS, subdomain enumeration from public sources; brand/typo domains.
- IP/ASN footprint: ASN lookups, netblock ownership, cloud IP attribution.
- DNS records: A/AAAA/MX/TXT/SPF/DMARC/CNAME; zone data from public sources.
- Tech fingerprinting: frameworks, CDNs, WAFs, versions from public pages/headers.
- Exposure: public code repos, cloud storage buckets, exposed dashboards, internet-scan datasets, paste sites.
- People & creds: employees/roles, email formats, breach-corpus credential exposure (for spray/reuse testing when in scope).
- Documents/metadata: public files and their metadata (authors, software, internal paths).
2. Active recon (in-scope interaction)
- Host discovery: which in-scope hosts are alive.
- Port/service scanning: TCP/UDP, service + version detection; note rate limits.
- Web asset enumeration: virtual hosts, directories, endpoints, API specs, JS-referenced routes.
- Screenshotting web services at scale to triage quickly.
3. Common tooling
Amass / subfinder / assetfinder, dnsx, httpx, nmap / masscan / naabu, nuclei (for known-CVE triage), gowitness/aquatone, theHarvester, cloud-attribution tooling. Prefer the RoE-approved set; respect rate limits.
4. Output: the attack-surface inventory
Produce a living inventory that feeds the domain skills:
| Asset | Type (web/api/host/cloud) | Tech/version | Auth surface | Priority | Feeds skill |
Prioritize by exposure × likely impact. Hand web assets to web-app-pentest, APIs to api-security-audit, hosts to network-pentest, cloud to cloud-pentest/entra-cloud-pentest, mobile to mobile-pentest.
5. Blue-team note (remediation value)
Recon findings are attack-surface-reduction wins: retire stale subdomains/hosts, fix DNS hygiene (SPF/DMARC), remove exposed storage/dashboards, rotate leaked credentials, and monitor cert transparency for rogue domains.
See references/recon-checklist.md.
<sub>© 2026 noahfranklin · Part of the Gideon security suite · MIT License · Original work.</sub>
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.