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 agentmods add skills/zoom/zoom-plugin/webnpx skills add zoom/zoom-plugin --skill webgit clone --depth 1 https://github.com/zoom/zoom-pluginWhat 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 | $0.00035 | $0.00426 |
| Opus 5 | $0.00017 | $0.00213 |
| Sonnet 5 | $0.00007 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
contact-center/web 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.
This is a copy
94% identical to contact-center/web — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Zoom Contact Center SDK - Web
Official docs:
- https://developers.zoom.us/docs/contact-center/web/
- https://developers.zoom.us/docs/contact-center/web/sdk-reference/
Quick Links
- concepts/lifecycle-and-events.md
- examples/app-context-and-state.md
- references/web-reference-map.md
- troubleshooting/common-issues.md
Integration Modes
- Contact Center App in Zoom client:
- Zoom Apps SDK engagement APIs/events.
- External website embed:
- Campaign SDK/web scripts (
zoomCampaignSdkpattern). - Video client initialization pattern.
- Smart Embed:
- iframe +
postMessageevent contract.
Hard Guardrails
- For campaign SDK, gate calls behind
zoomCampaignSdk:ready. - Persist state by
engagementId. - Expect context switching and background app behavior.
- Validate CSP and allow-list settings before debugging logic.
Chaining
- For in-client app APIs and auth flows: ../../zoom-apps-sdk/SKILL.md
- For identity and OAuth: ../../oauth/SKILL.md
- For cobrowse workflow: ../../cobrowse-sdk/SKILL.md
Operations
- RUNBOOK.md - 5-minute preflight and debugging checklist.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 55 lines · 35 tokens per session scan A 8d8a3fa2638a
contact-center/web is a skill published in the GitHub repository zoom/zoom-plugin (7 stars, last pushed 25d ago), licensed MIT. It adds 35 tokens to every session and 426 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to contact-center/web, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
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…