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 engagement-timelinegit 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/engagement-timeline)<a href="https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/engagement-timeline"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/engagement-timeline/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/engagement-timeline"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/engagement-timeline.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.00162 | $0.01173 |
| Opus 5 | $0.00081 | $0.00587 |
| Sonnet 5 | $0.00032 | $0.00235 |
| Haiku 4.5 | $0.00016 | $0.00117 |
Grade A, and why
engagement-timeline 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 13d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engagement Timeline
Build a timeline of meetings and emails with an account or contact, then let the user double-click any engagement to see what was discussed.
Prerequisites
browse_engagements reads from the calendar, email, and meeting providers connected to ZoomInfo. It requires at least one active calendar, email, or meeting integration in the workspace. If nothing is connected, browse_engagements returns no results — say so plainly and point the user to their ZoomInfo admin rather than implying there has been no contact.
browse_engagements is free (no credits). The optional double-click step uses conversation_intelligence, which consumes AI credits.
Input
Provided via $ARGUMENTS:
- Scope — one of:
- An account: ZoomInfo company ID (preferred), or a company name/domain (resolve via
search_companies). - A contact: ZoomInfo contact ID (preferred), or a name + company (resolve via
search_contacts). - Neither: time-line the current user's own recent engagements across all accounts.
- An account: ZoomInfo company ID (preferred), or a company name/domain (resolve via
- How far back (optional) — default is the last 90 days. "Last quarter", "this year", "since January", or a specific range all work; for anything beyond 90 days the window slides (see Workflow).
- Type (optional) — meetings only, emails only, or both (default both).
Workflow
-
Resolve scope. Use a supplied ZoomInfo ID directly as
zoominfoCompanyIdorzoominfoContactId. Otherwise resolve a name/domain viasearch_companies/search_contactsand confirm the top match if it is ambiguous. With no scope, callbrowse_engagementswith no ID to get the user's own engagements. -
Set the window.
browse_engagementsaccepts a date range up to 90 days wide (engagementDateStart,engagementDateEnd), ending no more than a month in the future. Default to the last 90 days. For a longer history, slide the window backward in 90-day chunks (e.g. 0-90 days ago, then 90-180, then 180-270) and merge the results, stopping when a chunk comes back empty or you reach the user's requested horizon. Tell the user when you are looking back across multiple windows so the wait is expected.
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.
- 13d ago First seen · 63 lines · 162 tokens per session scan A ddd0624b2f0e
engagement-timeline is a skill published in the GitHub repository Zoominfo/zoominfo-mcp-plugin (7 stars, last pushed 8d ago), licensed MIT. It adds 162 tokens to every session and 1,173 once invoked, about $0.0008 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…