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 email-findergit 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/email-finder)<a href="https://agentmods.dev/skills/hunter-io/claude-plugin/email-finder"><img src="https://agentmods.dev/badge/skills/hunter-io/claude-plugin/email-finder.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.00047 | $0.00577 |
| Opus 5 | $0.00023 | $0.00289 |
| Sonnet 5 | $0.00009 | $0.00115 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
email-finder 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.
What it actually says
Email Finder
Find the most likely email address for a person at a company using their name and domain.
Examples
/hunter:email-finder Jane Smith at stripe.com/hunter:email-finder the CEO of notion.so"What's John Doe's email at acme.com?""Find the email for Sarah Chen at Figma""How can I reach Marc Benioff at Salesforce?"
Steps
-
Parse the input. Extract the person's
full_nameand the companydomain.- "Jane Smith at Stripe" ->
full_name: "Jane Smith",domain: "stripe.com" - If the user provides a company name instead of a domain, infer the likely domain (e.g., "Stripe" -> "stripe.com")
- If only a role is given (e.g., "the CTO of Notion"), note that
Email-Finderrequires a name. Suggest usingDomain-Searchon the domain first to find the person's name, then come back to find their email.
- "Jane Smith at Stripe" ->
-
Call
Email-Finderwithfull_nameanddomain. -
Present the result:
# Email Found: Jane Smith @ Stripe
| Field | Value |
|-------|-------|
| **Email** | [email protected] |
| **Score** | 92 |
| **Domain** | stripe.com |
| **Verification** | valid |
## Sources
- stripe.com/team (last seen: 2026-02-15)
- LinkedIn profile (last seen: 2026-01-20)
## Next Actions
1. Verify this email address (Email-Verifier)
2. Save as a lead (Create-Lead-If-Missing — adds without overwriting an existing lead)
3. Enrich this contact with more details (Person-Enrichment)
4. Find more contacts at stripe.com (Domain-Search)
- If no email is found, suggest alternatives:
- "I couldn't find an email for [name] at [domain]. Would you like me to search all contacts at [domain] instead? That might help find the right person."
- Suggest checking the spelling of the name or trying a different domain variation.
Credit Cost
Costs 1 search credit — only charged if an email is found.
Success Criteria
Email address returned with score and at least one source.
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 · 63 lines · 47 tokens per session scan A 16f66c470ba8
email-finder is a skill published in the GitHub repository hunter-io/claude-plugin (9 stars, last pushed 6d ago), licensed MIT. It adds 47 tokens to every session and 577 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…