Agent skill

osint-recon

Quellcode ansehen: coreyhaines31/cybersecurity-skills

#201Globales Ranking · von 201 SkillsCritical

Installation

npx skills add coreyhaines31/cybersecurity-skills --skill osint-recon

23

Installationen

EU-hosted inference API

Power your AI agent skills with open-source models.

Drop-in OpenAI-compatible API. No data leaves Europe.

MiniMax

MiniMax M3

$0.40 / $1.40

per M tokens

Z.ai

GLM 5.3 Flash

$0.20 / $0.60

per M tokens

MoonshotAI

Kimi K3

$4.00 / $18.00

per M tokens

DeepSeek

DeepSeek V4.1 Flash

$0.40 / $1.40

per M tokens

OSINT Recon — Open Source Intelligence Gathering

Systematically gather, analyze, and correlate publicly available information from open sources.

Ethics Check

Before proceeding, confirm:

  1. The investigation has a legitimate purpose (threat intel, authorized assessment, CTF, defensive research)
  2. You are only gathering publicly available information
  3. Results will not be used for harassment, stalking, or doxing

Refuse requests that target individuals for harassment or aggregate private information beyond what the objective requires.

Collection Techniques

Domain and Infrastructure OSINT

Run these to map a target's infrastructure:

whois <domain>                  # Registration data
dig any <domain>                # DNS records

Query certificate transparency for subdomains:

curl -s "https://crt.sh/?q=%25.<domain>&output=json" | jq -r '.[].name_value' | sort -u

Additional sources: SecurityTrails, DNSDumpster, ipinfo.io, bgp.he.net, Wayback Machine, Shodan, Censys.

Organization OSINT

  • Company registrations, filings, SEC records (public companies)
  • LinkedIn company page — employee count, roles, tech stack hints
  • Job postings — reveal internal tools, tech stack, pain points
  • Press releases and news articles
  • GitHub/GitLab organization pages and public repositories
  • Patent filings

Email and Username OSINT

  • Email format patterns (e.g., first.last@domain.com)
  • HaveIBeenPwned — check for breach exposure (check only, never distribute breach data)
  • PGP key servers for email discovery
  • Gravatar lookups for email-to-identity correlation

Document and File OSINT

  • Extract metadata from public documents: exiftool <file> reveals author, software, GPS, timestamps
  • Google dorking: site:<domain> filetype:pdf, site:<domain> filetype:xlsx
  • Pastebin and code paste site monitoring
  • Public cloud storage enumeration (S3 buckets, GCS buckets with predictable names)

Threat Intelligence

  • CVE databases for the target's technology stack
  • Exploit databases (exploit-db, searchsploit)
  • Threat feeds and IOC databases (VirusTotal, MalwareBazaar, OTX)
  • Abuse contact databases

Analysis

  • Cross-reference findings across multiple sources
  • Validate information with at least two independent sources
  • Build a timeline of events when investigating incidents
  • Map relationships between entities (people, domains, IPs, organizations)
  • Rate confidence: High (multiple corroborating sources), Medium (single reliable source), Low (unverified)

Output Format

# OSINT Report
## Objective: [what we're investigating and why]
## Target: [entity/domain/person]
## Date: [date]

### Collection Summary
| Source | Findings | Confidence |
|--------|----------|------------|

### Key Findings

#### Finding 1: [Title]
- **Source:** [where this was found]
- **Details:** [what was discovered]
- **Confidence:** High / Medium / Low
- **Relevance:** [why this matters to the objective]

### Correlations
[How different findings connect to each other]

### Intelligence Gaps
[What we couldn't find or verify]

### Recommendations
[Next steps and actionable intelligence]

Boundaries

  • Only use publicly available sources
  • Never attempt to access private or authenticated systems
  • Do not aggregate PII beyond what is necessary for the stated objective
  • Attribute all findings to their source
  • Rate confidence levels honestly — do not overstate certainty
  • If a finding could cause harm if misused, note the sensitivity
  • Refuse requests for doxing, stalking, or unauthorized surveillance

References

  • OSINT Framework (osintframework.com)
  • SANS OSINT resource list
  • Bellingcat Online Investigation Toolkit

Installationen

Installationen23
Globales Ranking#201 von 201

Sicherheitsprüfung

athSafe
socketCritical
Warnungen: 1Bewertung: 90
snykMedium
WEB DATA FOR AGENTS

Give agents clean web context

Search and extract the public web as Markdown or structured JSON through one API or hosted MCP server.

Explore Webstractor

So verwenden Sie diesen Skill

1

Install osint-recon by running npx skills add coreyhaines31/cybersecurity-skills --skill osint-recon in your project directory. Führen Sie den obigen Installationsbefehl in Ihrem Projektverzeichnis aus. Die Skill-Datei wird von GitHub heruntergeladen und in Ihrem Projekt platziert.

2

Keine Konfiguration erforderlich. Ihr KI-Agent (Claude Code, Cursor, Windsurf usw.) erkennt installierte Skills automatisch und nutzt sie als Kontext bei der Code-Generierung.

3

Der Skill verbessert das Verständnis Ihres Agenten für osint-recon, und hilft ihm, etablierte Muster zu befolgen, häufige Fehler zu vermeiden und produktionsreifen Code zu erzeugen.

Was Sie erhalten

Skills sind Klartext-Anweisungsdateien — kein ausführbarer Code. Sie kodieren Expertenwissen über Frameworks, Sprachen oder Tools, das Ihr KI-Agent liest, um seine Ausgabe zu verbessern. Das bedeutet null Laufzeit-Overhead, keine Abhängigkeitskonflikte und volle Transparenz: Sie können jede Anweisung vor der Installation lesen und prüfen.

Kompatibilität

Dieser Skill funktioniert mit jedem KI-Coding-Agenten, der das skills.sh-Format unterstützt, einschließlich Claude Code (Anthropic), Cursor, Windsurf, Cline, Aider und anderen Tools, die projektbezogene Kontextdateien lesen. Skills sind auf Transportebene framework-agnostisch — der Inhalt bestimmt, für welche Sprache oder welches Framework er gilt.

Data sourced from the skills.sh registry and GitHub. Install counts and security audits are updated regularly.