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/hunter-io/claude-plugin/lead-listsnpx skills add hunter-io/claude-plugin --skill lead-listsgit clone --depth 1 https://github.com/hunter-io/claude-pluginWhat 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.00065 | $0.01147 |
| Opus 5 | $0.00032 | $0.00574 |
| Sonnet 5 | $0.00013 | $0.00229 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
lead-lists 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 2d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lead Lists
Create leads lists, populate them with contacts, and organize them into folders.
Examples
/hunter:lead-lists Create a list of marketing leads from SaaS companies"Save these contacts to a new list called Q2 Outreach""Build a list from the domain search results""Merge my two fintech lists""Favorite my Q2 Outreach list"
Workflow
Step 1: Determine the source
- From a previous search — use contacts already found via Domain Search. (Discover returns companies/counts, not contacts with emails, so route Discover results through Domain Search first to get saveable contacts.)
- From specific emails/contacts — the user provides addresses directly.
- From a new search — run the discover / domain-search skills first, then save results.
Step 2: Create or pick the list
To reuse an existing list, List-Leads-Lists to browse and Get-Leads-List to read one. For a new list, call Create-Leads-List with a descriptive name. If the user gives none, suggest one from context (e.g., "Fintech CTOs - France - 2026-07-16").
Present the deep-link: "List created: https://hunter.io/leads?leads_list_id={id}"
Step 3: Add leads
For each contact, call Create-Lead-If-Missing with the contact's data and the new leads_list_id — it adds new leads but never overwrites an existing lead's fields, so sparse search data can't clobber contacts the user already maintains. Note: for an email that is already a lead, Create-Lead-If-Missing returns the existing record unchanged and does not add it to the new list — report those as already-existing / not added rather than counting them as added. (Create-Or-Update-Lead would add them to the list but overwrites their fields; use it only when the user explicitly wants that.) Lead-Exists checks first if unsure. Include all available fields (email, first_name, last_name, position, company, linkedin_url). Report progress ("Adding lead 5 of 20…").
Step 4: Organize
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.
- 2d ago First seen · 78 lines · 65 tokens per session scan A ea8e11ee8aca
lead-lists is a skill published in the GitHub repository hunter-io/claude-plugin (9 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 1,147 once invoked, about $0.0003 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.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.