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 personalize-emailgit 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/personalize-email)<a href="https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/personalize-email"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/personalize-email/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/personalize-email"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/personalize-email.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00163 | $0.05125 |
| Opus 5 | $0.00081 | $0.02563 |
| Sonnet 5 | $0.00033 | $0.01025 |
| Haiku 4.5 | $0.00016 | $0.00513 |
Grade A, and why
personalize-email 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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Personalize Email
Generate personalized email variants. Calls get_gtm_context(detailed: true) unconditionally, resolves the prospect, runs a relationship-context pre-flight, pulls signals + CRM context, and composes 1-3 variants tuned to the chosen use case. Iteratively refinable.
The bar — adapts by use case
The composition bar depends on what the email is trying to do. Don't force a cold-outbound frame onto a follow-up.
| Use case | Anchor for the variant | Pain-bridge required? |
|---|---|---|
cold_outbound |
Signal → pain → positioning chain (specific, recent, verifiable signal; concrete inferred pain; GTM-context value prop) | Yes — mandatory |
re_engagement |
Fresh new signal since the last contact → reconnection frame | Yes (lightweight — the signal IS the reason to reach back) |
discovery_follow_up |
Prior conversation reference → next-step framing | No (the prior touchpoint replaces the pain bridge) |
demo_recap |
Recap of what was shown / heard → concrete next step | No |
renewal |
Outcome recap → renewal moment + stakeholder ask | No (anchor is the contract, not a pain) |
expansion |
Existing outcome → adjacent need / persona | Pain-bridge ON the adjacent need, not the existing relationship |
objection_handling |
Acknowledge stated objection → reframe | No (the objection IS the anchor) |
chaser (treat as a re_engagement variant) |
One new fact or framing since the last send → "still relevant?" | No |
Universal — every variant: specific to this prospect (no template feel); concrete next action; honest about state; ≤ use-case length cap.
The rule in one line: never default to "let me find a pain" when the use case calls for "what happens next."
Always-on context: get_gtm_context
Call get_gtm_context(detailed: true) first. Parse offerings into:
offering_profile = { offering, pain_points[], value_props[], proof_bank[], cta_ladder[] }
Anchor on one offering_profile. Pick one value_prop. Never invent stats or customer names — only what GTM context / proof_bank provides.
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 · 347 lines · 163 tokens per session scan A b68af3994adf
personalize-email is a skill published in the GitHub repository Zoominfo/zoominfo-mcp-plugin (7 stars, last pushed 6d ago), licensed MIT. It adds 163 tokens to every session and 5,125 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…
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…