Recon and Osint

Use when starting an assessment and you need to discover an application's full attack surface — subdomains, hosts, endpoints, technologies, exposed services, leaked credentials and secrets — on assets you own or are authorized to test. Feeds the threat model with real, not assumed, targets.

49 stars 7 forksSecurity Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add mn-youssef/security-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add mn-youssef/security-skills --skill recon-and-osint
Manual install
git clone --depth 1 https://github.com/mn-youssef/security-skills.git /tmp/security-skills
mkdir -p ~/.claude/skills
cp -r /tmp/security-skills/skills/recon-and-osint ~/.claude/skills/recon-and-osint

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Recon & OSINT (RECON phase — the front of the lifecycle)

## Overview
Find what's actually exposed before deciding what to test. Threat modeling assumes a surface;
recon *discovers* it. Most breaches start at an asset the defender forgot they had.

**Core principle:** You can't protect what you don't know exists. Enumerate everything first.

## ⚠️ Authorization
Only enumerate assets you own or are explicitly authorized to test. Passive OSINT on your own
org is always safe; active scanning/brute-forcing requires the asset to be in scope.

## Method (passive → active)
1. **Passive footprint** (no packets to target) — search engines, certificate transparency,
   public code, breach data, DNS records, archived pages. Zero noise, often highest value.
2. **Asset discovery** — subdomains, IP ranges, cloud buckets, related domains, forgotten staging.
3. **Service & tech fingerprinting** — what's running, which versions, which frameworks/CMS.
4. **Content discovery** — hidden endpoints, directories, API routes, JS-referenced URLs, params.
5. **Secret & exposure hunting** — leaked keys/tokens in public repos, paste sites, JS bundles, archives.
6. **Consolidate** — turn findings into a target inventory the threat model can rank.

See `references/recon-playbook.md` for concrete tools and commands per step.

## Quick reference — what to hunt
| Category | Goldmine sources |
|----------|------------------|
| Subdomains | crt.sh / cert transparency, `subfinder`, `amass`, DNS brute-force |
Read the full skill on GitHub

Details

Skill name
recon-and-osint
Path
skills/recon-and-osint/SKILL.md
License
MIT
Repo updated
12 June 2026

FAQ

What does the Recon and Osint skill do?

Use when starting an assessment and you need to discover an application's full attack surface — subdomains, hosts, endpoints, technologies, exposed services, leaked credentials and secrets — on assets you own or are authorized to test. Feeds the threat model with real, not assumed, targets.

How do I install the Recon and Osint skill?

Claude Code plugin: /plugin marketplace add mn-youssef/security-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Recon and Osint popular?

It lives in mn-youssef/security-skills, which has 49 GitHub stars and 7 forks.

Related skills

Access Control Testing

49

mn-youssef/security-skills

Use when testing whether users can access data or actions they shouldn't — IDOR/BOLA, horizontal and vertical privilege escalation, multi-tenant isolation, forced browsing, function-level authorization (BFLA), and mass assignment. The #1 cause of real-world breaches.

Testing & QA

Active Pentest

49

mn-youssef/security-skills

Use when you need to actually run security tests against a running application you own or are authorized to test — the shared execution harness for lab/proxy/scanner setup, safe non-destructive execution, and standardized proof-of-concept capture that the find/exploit specialist skills rely on.

Security

API Security Testing

49

mn-youssef/security-skills

Use when testing REST, GraphQL, gRPC, or WebSocket APIs against the OWASP API Security Top 10 — object- and function-level authorization (BOLA/BFLA), excessive data exposure, mass assignment, unrestricted resource consumption, and GraphQL-specific abuse. For apps you own or are authorized to test.

Security

Security Code Audit

49

mn-youssef/security-skills

Use when you have application source code and want to find security vulnerabilities by reading it — covers OWASP Top 10 across frontend, backend API, and database. Produces a findings register with severity, file:line, and exploitability.

Security

Pentest Reporting

49

mn-youssef/security-skills

Use when turning security findings into a clear, actionable report — scoring severity with CVSS, writing findings with reproduction and impact, prioritizing remediation, producing an executive summary, and tracking retests to closure. The phase that makes testing matter.

Security

Security Hardening

49

mn-youssef/security-skills

Use when you have a security finding (from code audit or pentest) and need to fix it correctly with secure-coding patterns, then verify the fix actually closes it. Covers fixes for injection, access control, XSS, auth, secrets, and config across the stack.

Security

Browse the most popular Claude skills, all security skills, or write your own with the skills generator.