manage-leads

manage-leads is a skill for Claude Code from hunter-io/claude-plugin. It costs 58 tokens per session (1,040 once invoked), scanned A, original, MIT.

A skill for managing individual contacts, called leads, in Hunter, a service for finding and organizing professional email contacts.

In plain words
What is it for?
Use it to create, find, update, tag, organize, or delete Hunter leads and manage their built-in contact details.
Why use it?
It avoids handling lead records one by one through a separate interface and helps check for duplicates before adding or changing contacts.

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 create, find, update, tag, organize, or delete Hunter leads and manage their built-in contact details.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hunter-io/claude-plugin/manage-leads
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 manage-leads
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 manage-leads

README.md
[![agentmods](https://agentmods.dev/badge/skills/hunter-io/claude-plugin/manage-leads.svg)](https://agentmods.dev/skills/hunter-io/claude-plugin/manage-leads)
Your own site
<a href="https://agentmods.dev/skills/hunter-io/claude-plugin/manage-leads"><img src="https://agentmods.dev/badge/skills/hunter-io/claude-plugin/manage-leads.svg" alt="Measured on agentmods" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,040 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.00058 $0.01040
Opus 5 $0.00029 $0.00520
Sonnet 5 $0.00012 $0.00208
Haiku 4.5 $0.00006 $0.00104

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

Security

Grade A, and why

manage-leads 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/manage-leads/SKILL.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Manage Leads

Create, update, tag, and organize the leads in a Hunter account.

Examples

  • /hunter:manage-leads Add [email protected] as a lead and tag her "priority"
  • "Update John's position to VP of Sales"
  • "Tag all these contacts as 'Q2 campaign'"
  • "Add a custom attribute 'deal size' to my leads"
  • "Delete the leads I imported by mistake"
  • "Do I already have [email protected] as a lead?"

Workflow

Create or update leads

  • Add a leadCreate-Lead-If-Missing to add without touching an existing lead's data, or Create-Or-Update-Lead when the user intends to update in place (it overwrites existing fields). Create-Lead forces a new record.
  • Check firstLead-Exists to test whether an email is already a lead; Get-Lead / List-Leads to read.
  • EditUpdate-Lead with the lead ID and the fields to change.

Include all available built-in fields when creating (email, first_name, last_name, position, company, linkedin_url, phone_number). Custom-attribute values can't be set through the lead tools (see Custom attributes below) — only the built-in fields are accepted.

Tags

  • Manage the tag vocabulary → List-Lead-Tags, Create-Lead-Tag, Update-Lead-Tag, Delete-Lead-Tag.
  • Apply/remove on a lead → Add-Tag-To-Lead, Remove-Tag-From-Lead.
  • If the user references a tag that doesn't exist yet, offer to create it before applying.

Custom attributes

  • Manage the definitions: List-Custom-Attributes to see them, Create-Custom-Attribute to add one (a label only — there is no type parameter), and Get-Custom-Attribute / Update-Custom-Attribute / Delete-Custom-Attribute to manage.
  • Note: the lead write tools expose only the built-in fields (email, name, position, company, …). There is currently no API to set a custom attribute's value on a lead, so this skill manages attribute definitions, not their per-lead values.

Present a summary

# Lead Updated: Jane Smith ([email protected])

| Field | Value |
|-------|-------|
| **Position** | VP of Engineering |
| **Company** | Stripe |
| **Tags** | priority, Q2 campaign |

## Next Actions
1. Add her to a leads list (lead-lists skill)
2. Add her to an outreach sequence (build-sequences skill)
3. Push to your CRM (push-to-crm skill)

Read the full file on GitHub · 80 lines

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 · 80 lines · 58 tokens per session scan A 80dbe3ce927f

Subscribe to this mod's changes

manage-leads is a skill published in the GitHub repository hunter-io/claude-plugin (9 stars, last pushed 6d ago), licensed MIT. It adds 58 tokens to every session and 1,040 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.

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