Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Osint Footprinting

ASecurity

Map a target organization's external footprint and attack surface from public sources — domains, subdomains, IP ranges, exposed services, technologies, and organizational details. Use at the start of an engagement (or for attack-surface management) to see what an attacker sees. Authorized scope, public sources.

8 stars
0 votes
0 copies
0 views
Added 9/19/2026
ai-agentsgotestingsecurity

Security Analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned 9/19/2026

$npx -y skills add jassics/awesome-claude-security --skill osint-footprinting --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Osint Footprinting?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Osint Footprinting
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jassics-osint-footprinting/badge)](https://www.skillsdirectory.com/skills/jassics-osint-footprinting)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: osint-footprinting
description: >-
  Map a target organization's external footprint and attack surface from public
  sources — domains, subdomains, IP ranges, exposed services, technologies, and
  organizational details. Use at the start of an engagement (or for attack-surface
  management) to see what an attacker sees. Authorized scope, public sources.
---

# Goal

A structured, organized map of the target's internet-facing attack surface, built
from public/passive sources, ready to drive testing or defensive remediation.

# What to gather (see `reference.md` for sources)

1. **Domains & subdomains** — root domains, subdomains (passive DNS, CT logs),
   related/typosquat domains.
2. **IP space & hosting** — IP ranges, ASNs, cloud footprint, CDNs.
3. **Exposed services** — internet-reachable hosts/ports/services (passive sources
   like internet-wide scan datasets), web apps, login portals, remote access.
4. **Technologies** — stacks, frameworks, third-party services, email/DNS records
   (SPF/DMARC/MX).
5. **Organizational context** — business units, acquisitions, brands (each expands
   the surface), code repos and public assets.

# Steps

1. Confirm scope (which org/domains are authorized) — stay within it.
2. Collect from public/passive sources; avoid active scanning here (hand live hosts
   to `network-security:network-pentest` if/when authorized).
3. Organize by asset, deduplicate, and flag the most exposed/sensitive (admin
   portals, remote access, forgotten/legacy assets, dev/staging exposed to internet).
4. Map it — an attack-surface mindmap (`security-diagramming:mindmap`).

# Output

An attack-surface inventory: asset · type · service/tech · exposure · source · notes,
plus a prioritized list of where to test (offense) or remediate (defense). Feed
exposures to `exposure-discovery` and live hosts to `network-security`.

# Notes

Footprinting is passive and public-source — it shows the attacker's outside view.
Forgotten/legacy and dev/staging assets exposed to the internet are the highest-value
finds. Acquisitions and alternate brands quietly expand the surface — enumerate them.
Stay within the authorized scope even though sources are public.

Attribution

jassicsjassics
View sourceSee grades on GitHubMore from jassics →
SSkills Directory ProSkills Directory

Get any skill into Claude in one click.

Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills. $9/mo.

See Pro

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills Directory ProSkills Directory

Get any skill into Claude in one click.

Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills. $9/mo.

See Pro

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

696561 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes
View all in ai-agents →