- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add OpenOSINT/OpenOSINT --skill osint -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add OpenOSINT/OpenOSINT --skill osint -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add OpenOSINT/OpenOSINT --skill osint -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add OpenOSINT/OpenOSINT --skill osint -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/OpenOSINT/OpenOSINT/tree/HEAD/skills/osintDe l'éditeur
Invoked as /osint <target>: investigate the target below with the chain that fits it and write the Markdown report described at the end. If no target was given, ask for one.
Target: $ARGUMENTS
OpenOSINT runs real tools in Python and returns their real output. You orchestrate and summarize; you never invent results.
--allow-active, never set OPENOSINT_ALLOW_ACTIVE, never use scrape, username, email or subdomain brute-force unless the user explicitly asks for that tool by name. If an active tool would help, say so and ask.claim [tool: args], e.g. SPF is missing [exposure example.com]. No citation, no finding.Use the CLI first: it needs no API key, no AI provider and no MCP server, so it works on any agent. Put --json before the subcommand:
uvx --from openosint==2.38.2 openosint --json exposure example.com
uvx --from openosint==2.38.2 openosint --json dns example.com
uvx --from openosint==2.38.2 openosint --json rdap example.com
uvx --from openosint==2.38.2 openosint --json whois example.com
uvx --from openosint==2.38.2 openosint --json dorks example.com
uvx --from openosint==2.38.2 openosint --json gdelt "Example Corp"
uvx --from openosint==2.38.2 openosint --json ip 8.8.8.8
uvx --from openosint==2.38.2 openosint --json exposure example.com --checks email,registration
--json output has tool, target, timestamp, results and error; cite those.exposure grades A-F. Its TLS and header checks connect to the target on port 443; --checks email,registration never touches the target (use it when the user wants zero contact). --report PATH.html writes a printable report.dorks only builds search URLs and sends nothing.ip queries ipinfo.io; it works unkeyed at low volume, and IPINFO_TOKEN raises the limit.Use the MCP tools (search_whois, search_rdap, search_gdelt_geo, generate_dorks, search_ip, and the keyed ones) only when the openosint MCP server is already connected. They return the same data. Do not emulate a tool with whois or curl.
Keyed extras, offer only when they add something: search_shodan, search_censys, search_virustotal (domain/IP/hash), search_abuseipdb, search_breach. Details and variable names: references/keys.md.
Order and interpretation hints: references/workflows.md.
Markdown, in this order: Target and scope (what was run, what was deliberately not), Findings (one bullet per finding with its citation), Not checked / needs a key, Leads to verify. Keep tool errors visible in the report.
Passive open-source reconnaissance and external exposure checks for a domain, IP address or organization, using OpenOSINT (DNS, RDAP, WHOIS, email authentication, TLS, security headers, news mentions,
---name: osintdescription: Passive open-source reconnaissance and external exposure checks for a domain, IP address or organization…---# skills/osint/SKILL.mdVue d'ensemble
Passive open-source reconnaissance and external exposure checks for a domain, IP address or organization, using OpenOSINT (DNS, RDAP, WHOIS, email authentication, TLS, security headers, news mentions, search dorks). Use when the user asks to investigate, profile, recon or "look up" a domain, IP or company, or to check what a domain exposes to the internet. No API keys needed for the default flow.
FAQ
Téléchargez skills/osint/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/OpenOSINT/OpenOSINT.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.