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 enrich-contactgit 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/enrich-contact)<a href="https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/enrich-contact"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/enrich-contact/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/enrich-contact"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/enrich-contact.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.00045 | $0.00481 |
| Opus 5 | $0.00023 | $0.00241 |
| Sonnet 5 | $0.00009 | $0.00096 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
enrich-contact 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 12d 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.
What it actually says
Enrich Contact
Look up a single contact's full profile in ZoomInfo.
Input
The user will provide via $ARGUMENTS one of:
- An email address (e.g.,
[email protected]) - A name and company (e.g.,
Jane Smith at Acme Corp) - A phone number
- A LinkedIn URL
- A ZoomInfo person ID
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, especially if a fallback search is needed. -
Identify the best match key from the user's input:
- Email → use
emailparameter - Name + company → use
firstName,lastName,companyName - Full name + company → use
fullName,companyName - Phone → use
phone - LinkedIn URL → use
externalURL - Person ID → use
personId
- Email → use
-
Enrich the contact using
enrich_contactswith the identified parameters. -
If no match, try a fallback:
- If name + company failed, try
search_contactswithjobTitleorcompanyNamevariations — use lookupidvalues for any filters - Suggest alternative spellings or company names
- If name + company failed, try
Output Format
[Full Name] — [Title] at [Company]
| Field | Value |
|---|---|
| Department | |
| Management Level | |
| Direct Phone | |
| Mobile Phone | |
| Accuracy Score | |
| Location | |
| Company | |
| Company Industry | |
| Company Size | |
| Last Updated | |
| ZoomInfo Person ID |
If any fields are unavailable, omit them rather than showing blanks. Note the accuracy score prominently — anything below 80 deserves a flag.
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.
- 12d ago First seen · 58 lines · 45 tokens per session scan A 3bd9eda61191
enrich-contact is a skill published in the GitHub repository Zoominfo/zoominfo-mcp-plugin (7 stars, last pushed 8d ago), licensed MIT. It adds 45 tokens to every session and 481 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…