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 company-news-monitorgit 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/company-news-monitor)<a href="https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/company-news-monitor"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/company-news-monitor/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/company-news-monitor"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/company-news-monitor.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.00110 | $0.00574 |
| Opus 5 | $0.00055 | $0.00287 |
| Sonnet 5 | $0.00022 | $0.00115 |
| Haiku 4.5 | $0.00011 | $0.00057 |
Grade A, and why
company-news-monitor 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.
What it actually says
Company News Monitor
A fast read on what has happened at an account lately, and which of it is worth acting on.
Prerequisites
enrich_company_signals charges data credits — each news article or scoop returned counts as a record, but companies already under management (enriched within the last 12 months) are free. get_gtm_context (optional, for relevance flagging) is free. News and scoop availability depends on your ZoomInfo package.
Input
Provided via $ARGUMENTS:
- Company (required) — ZoomInfo company ID (preferred), or a name/domain to resolve via
search_companies. If none is supplied, ask which company. - Lens (optional) — e.g. "anything about expansion", "leadership changes only". Filters the digest.
Workflow
- Resolve the company. Use the ZoomInfo ID directly, or resolve a name/domain via
search_companies. - Pull news and events. Run
enrich_company_signalswithsignalTypes: ["NEWS", "SCOOP"]for the company. - Add a relevance lens (optional). If useful, call
get_gtm_context(free) so you can flag items that touch your offerings, a competitor, or a known priority. - Build the digest. Group items by type (funding, M&A, product, leadership/executive moves, expansion, financial results, partnerships, and general news), most recent first. For each, give the date, the headline, a one-line "so what", and the source. Do not editorialize beyond what the item supports.
Output Format
News & developments — [Company]
Grouped, most recent first:
[Category]
- [date] — [headline]. So what: [one line]. [source]
Worth acting on — the one or two items that create a timely outreach opening, if any, with the angle. Omit if nothing rises to that bar.
If nothing recent — say there is no notable recent news or scoop activity on file rather than padding the digest with stale or trivial items.
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 · 40 lines · 110 tokens per session scan A 4f63f311d76e
company-news-monitor is a skill published in the GitHub repository Zoominfo/zoominfo-mcp-plugin (7 stars, last pushed 8d ago), licensed MIT. It adds 110 tokens to every session and 574 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…
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…