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 prospectinggit 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/prospecting)<a href="https://agentmods.dev/skills/hunter-io/claude-plugin/prospecting"><img src="https://agentmods.dev/badge/skills/hunter-io/claude-plugin/prospecting/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hunter-io/claude-plugin/prospecting"><img src="https://agentmods.dev/badge/skills/hunter-io/claude-plugin/prospecting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 53 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00050 | $0.01277 |
| Opus 5.5 | $0.00020 | $0.00511 |
| Sonnet 5.5 | $0.00010 | $0.00255 |
| Haiku 4.5 | $0.00005 | $0.00128 |
Grade A, and why
prospecting 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 1mo 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prospecting
Chain Hunter tools into a complete prospecting workflow. Discover companies, find contacts, verify emails, and enrich -- all in one go.
Examples
/hunter:prospecting Find CTOs at fintech startups in France/hunter:prospecting decision-makers at Stripe, Notion, and Figma"Build me a list of marketing leads at SaaS companies in Germany""I need 20 VPs of Sales at mid-size tech companies""Find people to reach out to at companies using Salesforce in healthcare"
Workflow
For a quick starting point, you can call Plan-Prospecting-Flow with the user's goal to get a suggested end-to-end plan, then execute the steps below (or a refinement of it).
Step 1: Identify Companies
Parse the user's request to determine the starting point:
- Specific companies provided (e.g., "Stripe, Notion, Figma") -- skip to Step 2.
- Criteria provided (e.g., "fintech startups in France") -- call
Find-Companieswith the criteria as thequeryparameter. If the user is targeting people by role (e.g. "CTOs at fintech startups"), still start fromFind-Companies, then useDomain-Search's seniority/department filters in Step 2 to pull just those people. (Find-Peopleonly counts contacts per company -- use it to size the batch, not to list people.)
Whenever more than one company will be searched, present the list and get approval before running Domain-Search, because each Domain-Search spends credits (1 per 10 results) and single-company calls have no built-in batch-consent gate:
"I found [N] companies matching your criteria. Here are the results. Which should I search for contacts? Select specific companies or say 'proceed with all' — each Domain Search uses 1 credit per 10 results returned."
For long lists (>10), show the top results rather than all of them.
Step 2: Find Contacts
For each company, call Domain-Search with the company's domain. Use server-side filters:
- "CTOs" or "engineering leaders" ->
department: "it",seniority: "executive" - "marketing team" ->
department: "marketing" - "executives" or "C-suite" ->
seniority: "executive" - "senior people" ->
seniority: "senior,executive"
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.
- 1mo ago First seen · 107 lines · 50 tokens per session scan A 0097c60d76d6
prospecting is a skill published in the GitHub repository hunter-io/claude-plugin (8 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 1,277 once invoked, about $0.0002 per session on Opus 5.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
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…