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 push-to-crmgit 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/push-to-crm)<a href="https://agentmods.dev/skills/hunter-io/claude-plugin/push-to-crm"><img src="https://agentmods.dev/badge/skills/hunter-io/claude-plugin/push-to-crm.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.00057 | $0.00781 |
| Opus 5 | $0.00028 | $0.00391 |
| Sonnet 5 | $0.00011 | $0.00156 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
push-to-crm 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Push to CRM
Send leads from Hunter to a connected CRM.
Examples
/hunter:push-to-crm Push my Q2 leads to HubSpot"Send these contacts to Salesforce""Sync the fintech list to my CRM""Which CRMs do I have connected?"
Workflow
Step 1: Identify the target CRM
List-Connected-Appsto show the user's connected integrations;Get-Connected-Appfor details on one.- If nothing is connected, tell the user to connect a CRM in Hunter first (Settings → Integrations) — this skill can't create the connection.
Step 2: Identify the leads
Determine which leads to push. Push-Leads-To-CRM accepts only saved lead_ids or a leads_list_id — so if the "current selection" is unsaved Domain Search / finder results, first save them as leads (with the user's OK, via Create-Lead-If-Missing) and push those IDs. You can't push unsaved rows. lead_ids is capped at 100: for larger selections, save them to a leads list and push the leads_list_id instead (or batch the IDs in groups of 100 after confirming the total). Note: Create-Lead-If-Missing leaves an already-existing lead out of the new list, so pushing that new leads_list_id would skip those contacts — collect the full set of lead_ids (existing + new, via Lead-Exists / List-Leads) and push those IDs. Don't reach for Create-Or-Update-Lead just to force list membership — it overwrites the existing lead's fields; use it only if the user explicitly wants to update them.
Step 3: Confirm, then push
State the target app and how many records will be sent, and wait for explicit confirmation, because this writes data into an external system:
"This will push 40 leads to HubSpot. Confirm?"
Only after a "yes", call Push-Leads-To-CRM with the leads and the target app.
Step 4: Report the queued push
Push-Leads-To-CRM is asynchronous — it returns a queued status and the lead count, not per-record results. Report that; do not invent created/updated/skipped numbers.
# Push queued → HubSpot
**Leads queued:** 40 | **Status:** queued
The sync runs in the background — check HubSpot in a few moments to confirm the records.
## Next Actions
1. Push another list
2. Review the leads in HubSpot shortly
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 · 66 lines · 57 tokens per session scan A 29951a9cd315
push-to-crm is a skill published in the GitHub repository hunter-io/claude-plugin (9 stars, last pushed 6d ago), licensed MIT. It adds 57 tokens to every session and 781 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-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…