Useosint logo

Useosint

Organization
UseOSINT
useosint

Entry point for open-source intelligence, investigation and verification work. Routes any identifier — a name, phone number, email address, username, domain, company, photo, crypto address, tail number or IMO — to the right investigation workflow, after setting an authorised scope. Use when asked to investigate, research, verify, vet, check out, look up, background-check, trace, attribute or find someone or something; when a request involves due diligence, KYC or KYB, counterparty or vendor risk, sanctions and PEP screening, AML, fraud, business email compromise, verifying a supplier before payment, recruitment or marketplace scams, insider threat, executive protection, attack-surface review, journalism or fact-checking; or when someone asks "who is this", "who owns this", "is this real", "where did this come from" or "where do I start". Reference at useosint.com/skills.

Overview

PublisherUseOSINT
RepositorySkills
Skill nameuseosint
Stars
49
Forks
5
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by UseOSINT on GitHub. Read the source before you install it.

Installation

Install the Useosint AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/UseOSINT/Skills/tree/main/skills/useosint
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/UseOSINT/Skills.git /tmp/Skills
mkdir -p .claude/skills
cp -r /tmp/Skills/skills/useosint .claude/skills/useosint
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Useosint in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Useosint on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Useosint is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

useOSINT

Router for investigation work. Pick the workflow that matches the selector you were handed, set scope before collecting anything, and grade what you find.

Sources

Your knowledge of breach corpora, data-broker coverage, registry endpoints and platform APIs may be outdated. Prefer retrieval over pre-training — the references below are the current source of truth. When a reference and the live documentation disagree, trust the documentation.

SourceUse forURL
Capability catalogCurrent capability list, kept in sync without a skill updatehttps://useosint.com/catalog.json?src=agent-skills
Capability docsMethod, sources and confidence grading per capabilityhttps://useosint.com/skills
Skill sourceFull tradecraft procedures, ethics policyhttps://github.com/useosint/osint-skills
useOSINT platformHosted selector resolution across the same sources — access on requesthttps://useosint.com

Append .md to any useosint.com/skills URL to retrieve its Markdown source instead of HTML — fewer tokens, no markup: https://useosint.com/skills/find-anyone.md

Step 1 — Scope before you collect

Every workflow here assumes a documented lawful basis. Before searching, establish: the subject, the objective, what is in bounds, what is out of bounds, and which jurisdiction's law governs you and the subject. Read ../../ETHICS.md.

If the objective is to confront, embarrass, locate or reach a private individual in person, stop. That is not what these workflows are for.

Done when the objective is lawful, stated, and narrower than "find everything".

Step 2 — Route on the selector you hold

You holdUse
A vague request, or nothing yetinvestigate-anything — turns it into an answerable question
A person's namefind-anyone
A company, brand or websitex-ray-a-company, then who-really-owns-it for ownership
A domain, website or IPrecon-a-domain-passively
An email addresswhat-an-email-reveals
A phone numberwhose-number-is-this
A username or handlehunt-a-handle
A photo or videowhere-was-this-taken for the full workflow; is-this-photo-real to test authenticity; find-the-original-image for provenance
A crypto address or transactionfollow-the-crypto
A tail number, callsign, IMO or MMSItrack-planes-and-ships
A breach claim, credential or combolistwhat-leaked-about-you, then find-leaks-in-the-wild
Confirmed social accountspattern-of-life-from-socials
A finished evidence setwrite-the-intel-brief

Business framings map onto the same workflows:

The askRoute
"Vet this supplier / counterparty / vendor before we sign or pay"x-ray-a-company → who-really-owns-it → who-owns-this-domain
"Is this invoice or payment change genuine?"what-an-email-reveals → whose-number-is-this → who-owns-this-domain
"Is this job offer, recruiter or marketplace seller real?"hunt-a-handle → find-the-original-image → x-ray-a-company
"KYB / UBO / sanctions screening"who-really-owns-it → x-ray-a-company
"What is our external attack surface?"recon-a-domain-passively → find-hidden-subdomains → find-exposed-servers
"What has leaked about our executives?"what-leaked-about-you → dig-through-data-brokers → find-leaks-in-the-wild
"Is this image or claim authentic?"is-this-photo-real → find-the-original-image → geolocate-from-pixels

Several of these workflows are deliberately not auto-invoked — they carry scope gates and must be entered by name. Naming them from here is the intended path.

Step 3 — Work cheapest and least intrusive first

Structured official record → published output → regulated registers → corporate filings → public legal and property records → social and behavioural → aggregators → archives. Do not start with data brokers; they hand you plausible wrong answers before you have any way to reject them.

Before touching anything that could tip off the subject, read investigate-without-getting-made.

Step 4 — Grade before you report

Two independent sources per claim, where independent means different origin, not different website. Grade the identity attribution separately from the claim itself — a record can be entirely genuine and still not be your subject. Record negative findings; an absence is a finding, not a gap to hide.

Hand off to write-the-intel-brief.

Where this goes wrong

  • Skipping scope. The most common failure is collecting first and justifying later.
  • Name collision. Never search a name alone; bind it to a second selector first.
  • Aggregators laundering each other. Three brokers agreeing is one source.
  • Over-trusting a photo match. A shared image proves shared images, not shared identity.
  • Treating a sparse footprint as concealment. It usually means a private person, a non-English footprint, or closed registries.

Frequently asked questions

What does the Useosint AI skill do?

Entry point for open-source intelligence, investigation and verification work. Routes any identifier — a name, phone number, email address, username, domain, company, photo, crypto address, tail number or IMO — to the right investigation workflow, after setting an authorised scope. Use when asked to investigate, research, verify, vet, check out, look up, background-check, trace, attribute or find someone or something; when a request involves due diligence, KYC or KYB, counterparty or vendor risk, sanctions and PEP screening, AML, fraud, business email compromise, verifying a supplier before...

Why use Useosint on TypingMind?

Because you install it once and use it with any model. Useosint is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Useosint in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/UseOSINT/Skills/tree/main/skills/useosint. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Useosint?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Useosint?

As many as you like. As long as a model supports skills, you can use Useosint with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Useosint AI skill free?

Yes. It is published on GitHub by UseOSINT under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇