build-list

build-list is a skill for Claude Code from Zoominfo/zoominfo-mcp-plugin. It costs 66 tokens per session (921 once invoked), scanned A, original, MIT.

A list-building tool that finds contacts or companies matching a written description and returns the results in a structured table. It can filter by roles, seniority, industry, company size, location, technology, growth, and other business criteria.

In plain words
What is it for?
Use it to find targeted business contacts, such as senior technology leaders, or companies matching a market, size, location, revenue, or technology profile.
Why use it?
It removes the manual work of searching for prospects and applying many filters one by one. The results can be prepared for export with the fields you need.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

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

Good fit Use it to find targeted business contacts, such as senior technology leaders, or companies matching a market, size, location, revenue, or technology profile.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zoominfo/zoominfo-mcp-plugin/build-list
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.

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

Made for: Claude Code.

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 build-list

README.md
[![agentmods](https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/build-list/github.svg)](https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/build-list)
Your own site
<a href="https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/build-list"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/build-list/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.

agentmods 80×15 button for build-list

Your own site · 80×15
<a href="https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/build-list"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/build-list.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 921 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00066 $0.00921
Opus 5 $0.00033 $0.00461
Sonnet 5 $0.00013 $0.00184
Haiku 4.5 $0.00007 $0.00092

Measured 10d ago against content hash 5d0bea6a335b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

build-list 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.

skills/build-list/SKILL.md · 86 lines

How it starts

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

Build List

Build a targeted list of contacts or companies from ZoomInfo and output as a structured table.

Input

The user will describe what they want via $ARGUMENTS. Examples:

  • "CTOs at Series B+ startups in SF with 50-200 employees"
  • "VP of Sales at healthcare companies using Salesforce with 500+ employees"
  • "All SaaS companies in EMEA with $10M-$50M revenue"
  • "Directors of Engineering at companies similar to Datadog"
  • "Marketing leaders at Fortune 500 companies in financial services"

The user may also specify:

  • How many results they want (default: 25)
  • Whether they want contacts, companies, or both
  • Specific fields to include in the output

Workflow

  1. Determine list type: Is the user asking for contacts, companies, or both? Default to contacts if they mention titles/roles, companies if they mention firmographics only.

  2. Parse criteria from natural language into structured filters:

    • Job titles, management levels, departments, job functions → contact filters
    • Industry, employee count, revenue, geography, tech stack, company type → company filters
    • Growth rate, funding, rankings → company filters
  3. Resolve all filter values using lookup before searching. This is critical — do NOT guess values. For every filter you plan to use, call lookup with the corresponding field name to get the valid values and use the returned id values in your search parameters.

  4. Execute the search:

    • For contacts: Use search_contacts with all resolved filters. Sort by -contactAccuracyScore. Request up to 100 results.
    • For companies: Use search_companies with all resolved filters. Sort by -employeeCount or -revenue. Request up to 100 results.
    • For both: Search companies first, then search contacts at the top results.
  5. Enrich top results if the search returns limited detail:

    • Use enrich_contacts (batch of 10) or enrich_companies (batch of 10) on the top results to fill in emails, phones, and other details.

Read the full file on GitHub · 86 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. 10d ago First seen · 86 lines · 66 tokens per session scan A 5d0bea6a335b

Subscribe to this mod's changes

build-list is a skill published in the GitHub repository Zoominfo/zoominfo-mcp-plugin (7 stars, last pushed 6d ago), licensed MIT. It adds 66 tokens to every session and 921 once invoked, about $0.0003 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

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

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens