osint-research

Generates passive OSINT recon reports for domains, IPs, emails, persons, and companies from public sources.

4|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/hint-shu/deep-research --skill osint-research-hint-shu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: osint-research
Source: https://github.com/hint-shu/deep-research/tree/main/skills/osint-research
Command: npx skills add https://github.com/hint-shu/deep-research --skill osint-research-hint-shu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually gathering open-source intelligence on an entity (domain, IP, email, person, or company) means juggling dozens of disconnected tools like Whois, DNS, crt.sh, Wayback Machine, and Shodan, then stitching results together by hand. This Skill automates that pipeline into a single structured dossier with an audit trail, while enforcing strict safety rules: secrets are redacted, dump/leak sites are blocklisted, and raw responses are never written to disk unfiltered. ## Core Features & Use Cases - Multi-entity classification and recon: Automatically detects whether the target is a domain, IP, email, person, company, or GitHub user and runs the appropriate channels (Whois/DNS, crt.sh subdomains, Wayback snapshots, Shodan InternetDB, GitHub code search, optional theHarvester/subfinder). - Hybrid report generation: Produces a findings summary ranked CRITICAL to LOW, an entity dossier, a mermaid relationship graph, CSV artifacts (subdomains, emails, IPs), and a sources audit trail in .firecrawl/osint/<slug>/. - Built-in security guardrails: All channel output passes through an inbound blocklist filter and a secret redactor (AWS keys, GitHub tokens, Slack tokens, JWTs, private keys) before any disk write. - Use Case: Run /osint-research example.com before a vendor assessment to get a 10-15 minute passive recon report covering subdomains, exposed ports, leaked credentials in public code, and historical snapshots — with zero paid subscriptions. ## Quick Start Ask the AI to run an OSINT recon on a target, for example: run osint-research on example.com and give me the findings report.

Frequently Asked Questions about osint-research

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

FAQPage Schema
How do I run passive OSINT recon on a domain?▼

Pass the domain as the target argument, for example /osint-research example.com. The skill classifies the entity, runs Whois, DNS, crt.sh, Wayback, Shodan InternetDB, and dork channels in parallel, then writes a report with findings, dossier, and graph to .firecrawl/osint/<slug>/.

What OSINT sources does this skill query for free?▼

It uses Whois, DNS records, crt.sh certificate transparency, the Wayback Machine, Shodan InternetDB (no auth), and GitHub code search, plus optional theHarvester and subfinder CLIs. Tavily, Firecrawl, Exa, and Perplexity MCP tools add search and scraping without any paid subscription requirement.

Can I run OSINT on an email address or a person?▼

Yes. The entity classifier detects emails, quoted person names, IPs, domains, companies (via --company flag), and GitHub users (github: prefix). Each type triggers only the applicable channels, such as dork queries for emails and persons.

Does the skill protect against leaked secrets in results?▼

Yes. All channel output is piped through an inbound filter and a secret redactor before any disk write. The redactor detects AWS keys, GitHub tokens, Slack tokens, Stripe keys, JWTs, and PEM private keys, replacing them with truncated placeholders.

What happens if theHarvester or subfinder is not installed?▼

They are optional channels and are silently skipped with an install tip recorded in the report's channel status block. Required channels like Whois and DNS abort the run with a clear error if they fail.

Why are paste and breach dump sites blocked in OSINT results?▼

The skill enforces a non-overridable blocklist of dump and breach sites (pastebin, dehashed, breachforums, doxbin, and similar) at both outbound query and inbound result levels. This keeps recon passive and avoids handling stolen data; filtered URLs are logged by host only in sources.md.