email-finder

email-finder is a skill for Claude Code from hunter-io/claude-plugin. It costs 47 tokens per session (577 once invoked), scanned A, original, MIT.

A contact lookup tool that finds the most likely professional email address for a named person at a company. It uses the person's name and the company's internet domain.

In plain words
What is it for?
Use it to look up a person's business email, including contacts identified by their role after you know their name.
Why use it?
It helps when you know who you want to contact but cannot find their work email address.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the hunter plugin — 13 skills, 1 MCP server shipped together

Good fit Use it to look up a person's business email, including contacts identified by their role after you know their name.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hunter-io/claude-plugin/email-finder
Install

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.

Any agent
npx skills add hunter-io/claude-plugin --skill email-finder
Clone the repo
git clone --depth 1 https://github.com/hunter-io/claude-plugin

Made for: Claude Code.

Or install hunter, the plugin that ships this one along with the rest of its 13 skills, 1 MCP server.

Wrote 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.

agentmods badge for email-finder

README.md
[![agentmods](https://agentmods.dev/badge/skills/hunter-io/claude-plugin/email-finder.svg)](https://agentmods.dev/skills/hunter-io/claude-plugin/email-finder)
Your own site
<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>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 577 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 8d ago against content hash 16f66c470ba8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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.

skills/email-finder/SKILL.md · 63 lines

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

  1. Parse the input. Extract the person's full_name and the company domain.

    • "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-Finder requires a name. Suggest using Domain-Search on the domain first to find the person's name, then come back to find their email.
  2. Call Email-Finder with full_name and domain.

  3. 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)
  1. 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.

Changes

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.

  1. 8d ago First seen · 63 lines · 47 tokens per session scan A 16f66c470ba8

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 103 tokens

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…

microsoft/vscode · 72 tokens

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…

openai/codex · 114 tokens