Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/assafkip/huntkit/osintnpx skills add assafkip/huntkit --skill osintgit clone --depth 1 https://github.com/assafkip/huntkitWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00153 | $0.10871 |
| Opus 5 | $0.00077 | $0.05436 |
| Sonnet 5 | $0.00031 | $0.02174 |
| Haiku 4.5 | $0.00015 | $0.01087 |
Grade A, and why
osint scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://cavalier.hudsonrock.com/api/json/v2/osint-tools/search-by-domain?domain=target.com" | jq . How it starts
The opening of the file, as written. The whole thing — 847 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OSINT Skill v3.2
Systematic intelligence gathering on individuals. From a name or handle to a scored dossier with psychoprofile, career map, and entry points.
Phase Router
Determine entry point from context:
- New name/handle/URL, "пробей", "find out about" → Phase 0 (full cycle)
- "Add LinkedIn/Instagram data" to existing dossier → Phase 2 (extraction)
- "Build psychoprofile" from existing data → Phase 4
- "Rate completeness" of existing dossier → Phase 5
- "Reformat" or "present" findings → Phase 6
Default (full research request): Phase 0 → 1 → 1.5 → 2 → 3 → 4 → 5 → 6.
Environment
All API keys via environment variables. Never hardcode tokens.
PERPLEXITY_API_KEY— Perplexity Sonar (fast answers + deep research)EXA_API_KEY— Exa AI (semantic search, company/people research, deep research)TAVILY_API_KEY— Tavily (agent-optimized search + extract, $0.005/req basic)APIFY_API_TOKEN— Apify scraping (LinkedIn, Instagram, Facebook)JINA_API_KEY— Jina reader/search/deepsearchPARALLEL_API_KEY— Parallel AI searchBRIGHTDATA_MCP_URL— Bright Data MCP endpoint (full URL with token)MCPORTER_CONFIG— mcporter config path
Scripts
Run from skill dir: bash scripts/<name>.sh.
Each script validates env vars, exits with descriptive error + URL to get the key.
Search & Research:
diagnose.sh— run FIRST. Capability map of all tools.- Perplexity (first-pass default): when operating through Claude, call the MCP tool
mcp__perplexity-ask__perplexity_askdirectly. It returns an AI answer with citations (equivalent tosonarmode). Use the shell script forsearch(ranked web results),reason(reconcile contradictions), anddeep(long-form research) modes, or from bash pipelines. perplexity.sh—search <query>|sonar <query>(AI answer) |reason <query>(sonar-reasoning-pro, compare leads / reconcile contradictions) |deep <query>(deep research). Required byfirst-volley.shand any bash-only pipeline.tavily.sh—search <query>(basic $0.005) |deep <query>(advanced) |extract <url>exa.sh—search <query>|company <name>|people <name>|crawl <url>|deep <prompt>first-volley.sh "Name" "context"— parallel search, all engines at once.merge-volley.sh <outdir>— deduplicate and merge first-volley results.
What ships with it
37 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/dossier-template.md 2.9 KB
- references/content-extraction.md 3.2 KB
- references/platforms.md 4.6 KB
- references/psychoprofile.md 2.9 KB
- references/security-tools.json 14 KB
- references/tools.md 13 KB
- scripts/apify.sh 2.1 KB runs code
- scripts/brightdata.sh 2.1 KB runs code
- scripts/capture-evidence.sh 10 KB runs code
- scripts/check-collision.py 4.0 KB runs code
- scripts/check-collision.sh 3.0 KB runs code
- scripts/diagnose.sh 6.3 KB runs code
- scripts/exa.sh 3.6 KB runs code
- scripts/extract-intake.py 12 KB runs code
- scripts/findings-verify-hook.py 6.6 KB runs code
- scripts/first-volley.sh 3.0 KB runs code
- scripts/identity-lookup.sh 4.8 KB runs code
- scripts/ingest-client-document.sh 7.0 KB runs code
- scripts/jina.sh 1.5 KB runs code
- scripts/mcp-client.py 3.8 KB runs code
- scripts/merge-volley.sh 1.6 KB runs code
- scripts/meta_ad_library_normalize.py 6.0 KB runs code
- scripts/meta-ad-library-hidden-api.sh 86 KB runs code
- scripts/next-ev-id.sh 2.3 KB runs code
- scripts/package.json 21 B
- scripts/parallel.sh 1.9 KB runs code
- scripts/perplexity-playbook.sh 10 KB runs code
- scripts/perplexity.sh 5.1 KB runs code
- scripts/render-report.py 7.1 KB runs code
- scripts/run_actor.js 9.8 KB runs code
- scripts/run-actor.sh 1.7 KB runs code
- scripts/security-stack-ats.sh 11 KB runs code
- scripts/security-stack-extract.py 7.9 KB runs code
- scripts/security-stack.sh 4.8 KB runs code
- scripts/tavily.sh 2.3 KB runs code
- tests/fixtures/meta_ad_library_sample.json 483 B
- tests/test_meta_ad_library_normalize.py 1.5 KB runs code
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 847 lines · 153 tokens per session scan A d031cb055a04
osint is a skill published in the GitHub repository assafkip/huntkit (51 stars, last pushed 1mo ago), licensed MIT. It adds 153 tokens to every session and 10,871 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…