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 manage-leadsgit 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/manage-leads)<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>- 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.00058 | $0.01040 |
| Opus 5 | $0.00029 | $0.00520 |
| Sonnet 5 | $0.00012 | $0.00208 |
| Haiku 4.5 | $0.00006 | $0.00104 |
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.
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 lead →
Create-Lead-If-Missingto add without touching an existing lead's data, orCreate-Or-Update-Leadwhen the user intends to update in place (it overwrites existing fields).Create-Leadforces a new record. - Check first →
Lead-Existsto test whether an email is already a lead;Get-Lead/List-Leadsto read. - Edit →
Update-Leadwith 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-Attributesto see them,Create-Custom-Attributeto add one (a label only — there is no type parameter), andGet-Custom-Attribute/Update-Custom-Attribute/Delete-Custom-Attributeto 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)
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 · 80 lines · 58 tokens per session scan A 80dbe3ce927f
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.
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…