Skip to content

Liberty91LTD/cti-skills / skills/osint-methodology

osint-methodology

Verified

Structured OSINT collection methodology. Planning, collection techniques, search operators, and documentation. Loaded by the osint-researcher agent.

OSINT Collection Methodology

Collection Planning

Before collecting, define:

  1. Objective: What specific intelligence do we need?
  2. Scope: What sources are relevant? What's out of scope?
  3. Keywords: Search terms, aliases, IOCs to look for
  4. Time constraints: How recent must the intelligence be?
  5. Documentation: How will findings be recorded?

Source Categories

CategorySourcesBest For
Government advisoriesCISA, NCSC, CERT-EU, national CERTsAuthoritative threat alerts, vulnerability warnings
Vendor reportsMandiant, CrowdStrike, Microsoft, Recorded Future, TalosCampaign analysis, actor profiles, malware analysis
Security researchBlogs, conference talks, academic papersNovel techniques, deep dives, vulnerability research
UndergroundForum mirrors, paste sites, Telegram (public), leak aggregatorsThreat actor communications, credential dumps, tools
Code repositoriesGitHub, GitLabMalware source, PoC exploits, attacker tools, leaked configs
Certificate transparencycrt.sh, CensysDomain enumeration, infrastructure mapping
DNS/WHOISSecurityTrails, DomainTools, RiskIQ (via web search)Infrastructure relationships, historical records
News/mediaTech press, infosec news sitesIncident reports, geopolitical context
Social mediaX/Twitter, LinkedIn, Reddit (public)OPSEC failures, community intelligence, actor claims

Search Operator Cheat Sheet

Google Dorks

site:example.com filetype:pdf         # PDFs on a specific site
"threat actor" AND "APT28" -site:reddit.com  # Exclude noise
inurl:"/wp-content/uploads/" filetype:exe    # Exposed uploads
"index of" "/backup"                   # Directory listings
intitle:"login" site:*.example.com     # Login pages on subdomains

GitHub Search

org:target-org password                # Leaked credentials
filename:.env DB_PASSWORD              # Exposed environment files
"api_key" language:python              # Hardcoded API keys
"BEGIN RSA PRIVATE KEY"                # Exposed private keys

Certificate Transparency (crt.sh)

https://crt.sh/?q=%.example.com        # All certs for subdomains
https://crt.sh/?q=example.com&output=json  # JSON output

Shodan Dorks (via web)

ssl.cert.subject.cn:"example.com"      # Certificates for domain
http.title:"Dashboard" org:"Target"    # Web dashboards
product:"Cobalt Strike"                # C2 servers

Collection Process

1. Broad Sweep

Start with broad searches to understand what's available:

  • Search for the topic/actor/indicator across major sources
  • Note the quantity and quality of available information
  • Identify the most promising sources for deeper collection

2. Targeted Collection

Narrow down to specific sources and extract detailed intelligence:

  • Read full reports, not just headlines
  • Extract specific IOCs, TTPs, dates, and attribution claims
  • Note each source's perspective and potential biases

3. Source Assessment

Apply Admiralty Scale to every finding (per source-assessment skill):

  • Rate source reliability (A-F)
  • Rate information credibility (1-6)
  • Note whether information is corroborated across sources

4. Documentation

Record every finding with full attribution:

#### Finding: [Title]
- **Source**: [URL or description]
- **Source rating**: [Admiralty code, e.g., B2]
- **Date collected**: YYYY-MM-DD
- **Date of information**: YYYY-MM-DD (when was this information produced?)
- **Summary**: [Key intelligence extracted]
- **Relevance**: [How this relates to the collection objective]

Ethical and Legal Boundaries

  • Only access publicly available information
  • Do not create fake accounts or impersonate anyone
  • Do not attempt to access restricted systems
  • Respect robots.txt and terms of service
  • Be aware of data protection regulations (GDPR)
  • Do not engage with threat actors or participate in illegal activity

Related skills

When OSINT collection surfaces an indicator, route into the appropriate enrichment / pivot:

  • Bulk IOC enrichment — /ioc-enrichment-workflow chains /lookup-virustotal, /lookup-otx, /lookup-shodan, /lookup-abuseipdb, /lookup-greynoise, /lookup-urlscan, /lookup-censys, and /lookup-misp
  • Single-indicator first hop — /ip-investigation, /domain-investigation, /hash-investigation, /url-investigation
  • Multi-hop graph walk — /indicator-pivoting
  • Internal correlation against your own catalogue — /lookup-misp search-attributes / search-events
  • Ransomware victim-status sweeps on org names — /lookup-ransomwarelive search --q <orgname>
  • Underground forums and Telegram — /darkweb-collection (read its OPSEC primer before any DIY collection)
  • Apply rigor to the finished product — /score-source, /apply-tlp, /confidence-language, /likelihood-language
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall