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 contact-relationship-recapgit 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/contact-relationship-recap)<a href="https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/contact-relationship-recap"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/contact-relationship-recap/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/contact-relationship-recap"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/contact-relationship-recap.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.00124 | $0.00658 |
| Opus 5 | $0.00062 | $0.00329 |
| Sonnet 5 | $0.00025 | $0.00132 |
| Haiku 4.5 | $0.00012 | $0.00066 |
Grade A, and why
contact-relationship-recap 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.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contact Relationship Recap
Where we stand with one person, read from recent conversations: their posture toward us, and how it is changing.
Prerequisites
Contact-scoped conversation_intelligence requires at least one connected email or meeting source; conversation_intelligence and contact_research consume AI credits. If no conversation data exists for the person, give the contact_research-based read and note that conversation context was unavailable, pointing the user to their ZoomInfo admin.
Input
Provided via $ARGUMENTS:
- Contact (required) — ZoomInfo contact ID (preferred), or a name plus company to resolve via
search_contacts. - Lens (optional) — e.g. "is the champion still engaged", "did sentiment cool after the demo". Frames the recap.
Workflow
- Resolve the contact. Use the ZoomInfo contact ID directly; otherwise resolve via
search_contacts(name + company) and confirm an ambiguous match before spending credits. - Read the relationship. Run contact-scoped
conversation_intelligenceandcontact_researchin parallel. Ask CI what this person has raised across recent conversations, how engaged and positive they have been, what they have committed to, and whether their stance has shifted. Keep CI scoped to this one contact; it cannot search by topic or count mentions, and sees only the last few engagements. - Synthesize posture and trajectory. Classify the person's current posture (engaged champion, supportive, neutral, skeptical, gone quiet) and whether it is strengthening or weakening, with evidence. Do not infer a champion or a risk the conversations do not support.
Output Format
Where we stand with [Name] — [Title, Company]
Posture — one line: engaged champion / supportive / neutral / skeptical / gone quiet, with the evidence.
Recent from them — 3-5 bullets on what this person has actually said or asked for lately (from CI, with source meetings).
What's changed — shifts in engagement, tone, or influence; e.g. went quiet after a reorg, warmed up after a successful pilot. Tied to evidence.
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 · 44 lines · 124 tokens per session scan A f40bf9969e3e
contact-relationship-recap is a skill published in the GitHub repository Zoominfo/zoominfo-mcp-plugin (7 stars, last pushed 8d ago), licensed MIT. It adds 124 tokens to every session and 658 once invoked, about $0.0006 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…