exec-brief

exec-brief is a skill for Claude Code, Codex from Zoominfo/zoominfo-mcp-plugin. It costs 135 tokens per session (729 once invoked), scanned A, original, MIT.

A one-page preparation brief for an executive joining a sales call. It combines company research, information from earlier conversations, and research about the people attending.

In plain words
What is it for?
Use it to prepare an executive for a customer meeting by identifying the company and attendees, summarising account and conversation context, noting open issues and commitments, and highlighting the key action for the call.
Why use it?
An executive may have little time and no background on the account or discussion. The brief condenses who is involved, why the call matters, what has happened, and what remains open.

Skill for Claude CodeCodex

Part of the zoominfo plugin — 35 skills, 1 MCP server shipped together

Install

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.

agentmods
npx agentmods add skills/zoominfo/zoominfo-mcp-plugin/exec-brief
Any agent
npx skills add Zoominfo/zoominfo-mcp-plugin --skill exec-brief
Clone the repo
git clone --depth 1 https://github.com/Zoominfo/zoominfo-mcp-plugin

Made for: Claude Code, Codex.

Or install zoominfo, the plugin that ships this one along with the rest of its 35 skills, 1 MCP server.

Wrote 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.

agentmods badge for exec-brief

README.md
[![agentmods](https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/exec-brief.svg)](https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/exec-brief)
Your own site
<a href="https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/exec-brief"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/exec-brief.svg" alt="Measured on agentmods" height="20"></a>
Per session 135 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 729 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00135 $0.00729
Opus 5 $0.00068 $0.00365
Sonnet 5 $0.00027 $0.00146
Haiku 4.5 $0.00014 $0.00073

Measured 5d ago against content hash 0b768301fc1d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

exec-brief 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 5d 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.

skills/exec-brief/SKILL.md · 46 lines

How it starts

The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Exec Brief

One page an executive can absorb in the elevator: who, why now, where we stand, and the one thing to do in the room.

Prerequisites

conversation_intelligence requires at least one connected meeting or email source; account_research, contact_research, and conversation_intelligence consume AI credits. If no conversation data exists, build from research and note that the "where we stand" view is research-based only, pointing the user to their ZoomInfo admin.

Input

Provided via $ARGUMENTS:

  • Account (required) — ZoomInfo company ID (preferred), or a name/domain to resolve via search_companies.
  • The exec and the meeting (recommended) — who is being briefed, the meeting's purpose, and the attendees, so the one-pager is framed for their role.

Workflow

  1. Resolve the account (and key attendees, if named). Use ZoomInfo IDs directly, or resolve via search_companies / search_contacts.
  2. Gather, then compress. Run account_research (company + deal context) and account-scoped conversation_intelligence (recent state, open threads, commitments) in parallel. Run contact_research only for attendees the user named or that research surfaces as the key deal contacts; if no attendees are known, ask before spending contact_research credits rather than researching the whole account. Keep CI scoped to the account; it sees only the last few engagements.
  3. Write for an exec. Ruthlessly compress to one page. Lead with why this account matters and why now. Give the exec the single most useful thing to do or say, and the landmines to avoid. Cut firmographic detail that does not change how they show up. Every line earns its place; attribute the relationship claims.

Output Format

Exec brief — [Company]

Bottom line (2-3 sentences) — who they are, why this meeting matters, and where the relationship stands right now.

Where we stand — 2-3 bullets on the deal/relationship state and what is currently open (from CI + research).

Read the full file on GitHub · 46 lines

Changes

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.

  1. 5d ago First seen · 46 lines · 135 tokens per session scan A 0b768301fc1d

Subscribe to this mod's changes

exec-brief is a skill published in the GitHub repository Zoominfo/zoominfo-mcp-plugin (7 stars, last pushed yesterday), licensed MIT. It adds 135 tokens to every session and 729 once invoked, about $0.0007 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens