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 Zoominfo/zoominfo-mcp-plugin --skill recommend-contactsgit clone --depth 1 https://github.com/Zoominfo/zoominfo-mcp-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/zoominfo/zoominfo-mcp-plugin/recommend-contacts)<a href="https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/recommend-contacts"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/recommend-contacts/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/recommend-contacts"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/recommend-contacts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00033 | $0.01088 |
| Opus 5 | $0.00016 | $0.00544 |
| Sonnet 5 | $0.00007 | $0.00218 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
recommend-contacts 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 10d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recommended Contacts
Get ML-ranked contact recommendations at a target company, personalized to your ZoomInfo usage and CRM data.
Input
The user will provide via $ARGUMENTS:
- A company name, domain, or ZoomInfo company ID (required)
- Optionally: a use case — "prospecting", "deal acceleration", or "renewal" (defaults to PROSPECTING)
- Optionally: how many results they want (defaults to 25, max 100)
Workflow
-
Lookup metadata first — before calling any other MCP tool, use
lookupto load reference data for any fields relevant to the request. Use the returnedidvalues (not display names) in all subsequent API calls. This ensures accurate parameter resolution and result interpretation. -
Resolve the company if the user provided a name or domain:
- Use
search_companieswithcompanyNameorcompanyWebsiteto find the company — use lookupidvalues for any filters. - Extract the ZoomInfo company ID from the result.
- Use
-
Enrich the company using
enrich_companieswith the resolvedcompanyIdto get firmographic context (industry, size, revenue, business model). This context is used to interpret the recommendations. -
Map the use case to the correct enum value:
- "prospecting" or default →
PROSPECTING(based on contacts you've viewed, copied, or exported on the ZoomInfo platform; has cold-start support) - "deal acceleration" or "new business" →
DEAL_ACCELERATION(based on contacts in closed-won CRM opportunities for new business) - "renewal", "growth", or "expansion" →
RENEWAL_AND_GROWTH(based on contacts in closed-won CRM opportunities for renewals)
- "prospecting" or default →
-
Get recommendations using
get_recommended_contactswith:ziCompanyId: the resolved ZoomInfo company IDuseCaseType: the mapped enum valuepageSize: user-specified count or 25
-
Enrich the top contacts using
enrich_contactson the top 10 results (batch of 10) to get full contact details including email, direct phone, and accuracy scores.
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.
- 10d ago First seen · 83 lines · 33 tokens per session scan A 18fb962541ca
recommend-contacts is a skill published in the GitHub repository Zoominfo/zoominfo-mcp-plugin (7 stars, last pushed 6d ago), licensed MIT. It adds 33 tokens to every session and 1,088 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…