build-zoom-virtual-agent

build-zoom-virtual-agent is a skill for Claude Code from anthropics/knowledge-work-plugins. It costs 44 tokens per session (812 once invoked), scanned A, original, Apache-2.0.

A reference guide for adding Zoom Virtual Agent experiences to websites and mobile apps. A virtual agent is a software assistant that chats with users, often using a connected knowledge base to answer questions.

In plain words
What is it for?
Use it to embed chat on a website, wrap that chat in Android or iOS apps, sync a knowledge base, or troubleshoot the agent's lifecycle.
Why use it?
It brings together the setup and lifecycle details needed for web embeds, mobile wrappers, and knowledge-base updates. It also helps separate website chat work from native mobile integration and backend API work.

Skill for Claude Code ✓ vendor

Written for Claude Code: shipped in a Claude Code plugin.

Part of the zoom-plugin plugin — 43 skills shipped together

Good fit Use it to embed chat on a website, wrap that chat in…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/anthropics/knowledge-work-plugins/virtual-agent
About the project

Knowledge Work Plugins is an open-source collection of Claude extensions organized around roles such as productivity, sales, and customer support. Each plugin combines role-specific guidance, connectors, commands, and sub-agents so knowledge workers can use Claude with their team’s tools and processes. The catalogue entries are examples of, or workflows from, this plugin collection.

anthropics/knowledge-work-plugins · 23,902 stars · on GitHub

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 anthropics/knowledge-work-plugins --skill virtual-agent
Clone the repo
git clone --depth 1 https://github.com/anthropics/knowledge-work-plugins

Made for: Claude Code.

Or install zoom-plugin, the plugin that ships this one along with the rest of its 43 skills.

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-zoom-virtual-agent

README.md
[![agentmods](https://agentmods.dev/badge/skills/anthropics/knowledge-work-plugins/virtual-agent.svg)](https://agentmods.dev/skills/anthropics/knowledge-work-plugins/virtual-agent)
Your own site
<a href="https://agentmods.dev/skills/anthropics/knowledge-work-plugins/virtual-agent"><img src="https://agentmods.dev/badge/skills/anthropics/knowledge-work-plugins/virtual-agent.svg" alt="Measured on agentmods" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 812 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.00044 $0.00812
Opus 5 $0.00022 $0.00406
Sonnet 5 $0.00009 $0.00162
Haiku 4.5 $0.00004 $0.00081

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

Security

Grade A, and why

build-zoom-virtual-agent 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 2d 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

partner-built/zoom-plugin/skills/virtual-agent/SKILL.md · 74 lines

How it starts

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

/build-zoom-virtual-agent

Background reference for Zoom Virtual Agent across:

  • Web campaign/chat embeds.
  • Android WebView wrappers.
  • iOS WKWebView wrappers.
  • Knowledge-base sync and custom API ingestion.

Official docs:

Routing Guardrail

  1. concepts/architecture-and-lifecycle.md
  2. scenarios/high-level-scenarios.md
  3. references/versioning-and-drift.md
  4. references/samples-validation.md
  5. references/environment-variables.md
  6. troubleshooting/common-drift-and-breaks.md
  7. RUNBOOK.md

Platform skills:

Common Lifecycle Pattern

  1. Configure campaign or entry ID in Virtual Agent admin.
  2. Initialize SDK in web or WebView container.
  3. Wait for readiness (zoomCampaignSdk:ready or waitForReady()) before calling APIs.
  4. Register bridge handlers (exitHandler, commonHandler, support_handoff) when native orchestration is needed.
  5. Handle conversation lifecycle (engagement_started, engagement_ended) and UI state.
  6. End chat (endChat) and clean up listeners.

Read the full file on GitHub · 74 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. 2d ago First seen · 74 lines · 44 tokens per session scan A 5f41eeb6b6ec

Subscribe to this mod's changes

build-zoom-virtual-agent is a skill published in the GitHub repository anthropics/knowledge-work-plugins (23,902 stars, last pushed yesterday), licensed Apache-2.0. It adds 44 tokens to every session and 812 once invoked, about $0.0002 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-09-05.

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