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/discovernpx skills add hunter-io/claude-plugin --skill discovergit 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/discover)<a href="https://agentmods.dev/skills/hunter-io/claude-plugin/discover"><img src="https://agentmods.dev/badge/skills/hunter-io/claude-plugin/discover.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00059 | $0.01144 |
| Opus 5 | $0.00030 | $0.00572 |
| Sonnet 5 | $0.00012 | $0.00229 |
| Haiku 4.5 | $0.00006 | $0.00114 |
Grade A, and why
discover 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 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.
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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discover
Find companies matching any criteria and size how many contacts they hold — all free, no credits consumed. To turn companies into named, verified contacts you then use Domain Search (which consumes credits); for the full "find people by role" pipeline, use the prospecting skill.
Examples
/hunter:discover fintech startups in France/hunter:discover SaaS companies using Salesforce"Find healthcare companies in Germany with 100+ employees""How many contacts could I get across these fintech companies?""Series B startups in Europe""Save this search as 'French fintech'""Run my saved search"
Steps
-
Find companies. Pass the user's query directly to
Find-Companiesas thequeryparameter — it accepts natural language and handles parsing. -
Present the results:
# Discover: Fintech Startups in France
**Found:** 43 companies | **Showing:** 10
| Company | Domain | Industry | Size | Location |
|---------|--------|----------|------|----------|
| Qonto | qonto.com | Fintech | 150 | Paris, FR |
| Pennylane | pennylane.com | Fintech | 120 | Paris, FR |
| Swan | swan.io | Fintech | 95 | Paris, FR |
| ... | ... | ... | ... | ... |
## Next Actions
1. Narrow or refine the criteria to surface different results (Find-Companies / Find-People have no offset paging)
2. Find the actual contacts at one of these (Domain-Search — consumes credits)
3. Estimate how many contacts these companies hold, free (see "Sizing a batch" below)
4. Save companies to a list (company-lists skill)
5. Run the full people pipeline on these (prospecting skill)
6. Rerun one of your saved searches (List-Saved-Searches)
-
If results are too broad (hundreds of companies), suggest narrowing: "That's a broad search. Try adding filters like industry, size, location, or technology."
-
If zero results, suggest loosening criteria: "No companies matched. Try broadening — for example, widen the location or employee range."
-
Remind users this is free: "Discovering companies is free — refine as many times as you'd like. You only spend credits when you pull the actual contacts with Domain Search."
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 · 76 lines · 59 tokens per session scan A 067899659fb8
discover is a skill published in the GitHub repository hunter-io/claude-plugin (9 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 1,144 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.
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…