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 skills add hunter-io/claude-plugin --skill domain-searchgit clone --depth 1 https://github.com/hunter-io/claude-pluginWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hunter-io/claude-plugin/domain-search)<a href="https://agentmods.dev/skills/hunter-io/claude-plugin/domain-search"><img src="https://agentmods.dev/badge/skills/hunter-io/claude-plugin/domain-search.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
What 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.1 | $0.00044 | $0.00874 |
| Opus 5 | $0.00022 | $0.00437 |
| Sonnet 5 | $0.00009 | $0.00175 |
| Haiku 4.5 | $0.00004 | $0.00087 |
Grade A, and why
domain-search scanned grade A with 0 findings 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 8d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Search
Find all contacts and email addresses associated with a company domain.
Examples
/hunter:domain-search stripe.com/hunter:domain-search Notion"Who works at figma.com?""Find me contacts at Salesforce""Show me the marketing team at hubspot.com""List executives at acme.com"
Steps
-
Parse the input. Extract the
domain.- "stripe.com" -> use directly
- "Stripe" or "stripe" -> infer domain as "stripe.com"
- If unsure about the domain, ask the user to confirm.
Free pre-check first (optional). If the user wants to size how many contacts/emails Hunter has for a domain before paying, call
Email-CountbeforeDomain-Search. It's free and takes adomainplus an optionalpersonal/generictype. It returns email totals only — not company headcount (use company-enrichment for employee counts) — and can't filter the count by role or department (only the paidDomain-Searchfilters by seniority/department). -
Call
Domain-Searchwith thedomain. Use server-side filters when the user specifies criteria:type:personalorgenericseniority: comma-separated fromjunior,senior,executivedepartment: comma-separated fromexecutive,it,finance,management,sales,legal,support,hr,marketing,communication,education,design,health,operations,product,research,consulting,administrative,procurementrequired_field:full_name,position, orphone_number— only return results where this field has a valuelimit: 1-100 (default 10)offset: for pagination
Mapping user requests to filters:
- "marketing team" ->
department: "marketing" - "executives" / "C-suite" / "leadership" ->
seniority: "executive" - "engineering" / "developers" ->
department: "it" - "senior people" ->
seniority: "senior,executive" - No filter specified -> show the top contacts by confidence score
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.
- 8d ago First seen · 81 lines · 44 tokens per session scan A abc8918e51ef
domain-search is a skill published in the GitHub repository hunter-io/claude-plugin (9 stars, last pushed 6d ago), licensed MIT. It adds 44 tokens to every session and 874 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…