performing-open-source-intelligence-gathering

Collects public intelligence on target organizations to map attack surfaces and plan red team engagements.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill performing-open-source-intelligence-gathering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performing-open-source-intelligence-gathering
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/red-teaming/performing-open-source-intelligence-gathering
Command: npx skills add https://github.com/xalgord/xalgorix --skill performing-open-source-intelligence-gathering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Red team operators need a structured methodology for gathering publicly available information about a target organization before an engagement, and ad-hoc reconnaissance often misses breach credentials, leaked secrets, and subdomains that provide the fastest path to initial access.

Core Features & Use Cases

  • Four-Phase OSINT Workflow: Covers domain and network reconnaissance, personnel and social intelligence, credential and data leak discovery, and technology stack identification.
  • MITRE ATT&CK Mapping: Aligns activities with reconnaissance techniques including T1595, T1589, T1590, T1591, and T1593 for standardized reporting.
  • Commonly Missed Sources: Highlights breach dumps, GitHub dorking, certificate transparency logs, and document metadata extraction with confirmation steps before reporting.
  • Use Case: During an authorized red team engagement, an operator follows the workflow to enumerate subdomains with Amass and Subfinder, harvest employee emails via LinkedIn and Hunter.io, and check HaveIBeenPwned for leaked credentials to build a spearphishing target profile.

Quick Start

Ask the AI to perform OSINT gathering against an authorized target domain, enumerating subdomains, employees, leaked credentials, and technology stack into a structured reconnaissance report.

Frequently Asked Questions about performing-open-source-intelligence-gathering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform OSINT gathering for a red team engagement?

Follow a four-phase workflow: enumerate domains and subdomains via certificate transparency and DNS brute-forcing, map personnel through LinkedIn and email conventions, search breach databases and GitHub for leaked credentials, and fingerprint the technology stack using job postings and Wappalyzer.

What tools are used for subdomain enumeration and reconnaissance?

Amass and Subfinder handle subdomain enumeration, theHarvester collects emails and names, and Shodan or Censys identify exposed services. SpiderFoot and Recon-ng automate broader OSINT collection across multiple sources.

Which OSINT sources are most often missed during reconnaissance?

Breach and credential dumps like HaveIBeenPwned and Dehashed are the most-skipped source and often the fastest path to initial access. GitHub dorking for secrets and document metadata extraction with exiftool are also frequently overlooked.

Is OSINT gathering legal without authorization?

No. This skill is intended for authorized security testing and educational purposes only. Gathering intelligence against organizations without written permission may violate computer fraud laws, so always obtain proper authorization first.

How do I validate OSINT findings before reporting them?

Confirm leaked credentials and assets are actually live through in-scope authentication tests and DNS resolution. Do not conclude nothing was found until both passive sources like CT logs and active sources like subdomain brute-forcing are exhausted.