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/video-sdknpx skills add zoom/zoom-plugin --skill video-sdkgit 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.00039 | $0.03381 |
| Opus 5 | $0.00019 | $0.01690 |
| Sonnet 5 | $0.00008 | $0.00676 |
| Haiku 4.5 | $0.00004 | $0.00338 |
Grade A, and why
build-zoom-video-sdk-app scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl "https://source.zoom.us/videosdk/zoom-video-{VERSION}.min.js" -o js/zoom-video-sdk.min.js How it starts
The opening of the file, as written. The whole thing — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/build-zoom-video-sdk-app
Background reference for fully custom video-session products. Prefer plan-zoom-product first when the boundary between Meeting SDK and Video SDK is still unclear.
Build custom video experiences powered by Zoom's infrastructure.
Hard Routing Guardrail (Read First)
- If the user asks for custom real-time video app behavior (topic/session join, custom rendering, attach/detach), route to Video SDK.
- Do not switch to REST meeting endpoints for Video SDK join flows.
- Video SDK does not use Meeting IDs,
join_url, or Meeting SDK join payload fields (meetingNumber,passWord).
Meeting SDK vs Video SDK
| Feature | Meeting SDK | Video SDK |
|---|---|---|
| UI | Default Zoom UI or Custom UI | Fully custom UI (you build it) |
| Experience | Zoom meetings | Video sessions |
| Branding | Limited customization | Full branding control |
| Features | Full Zoom features | Core video features |
UI Options (Web)
Video SDK gives you full control over the UI:
| Option | Description |
|---|---|
| UI Toolkit | Pre-built React components (low-code) |
| Custom UI | Build your own UI using the SDK APIs |
Prerequisites
- Zoom Video SDK credentials from Marketplace
- SDK Key and Secret
- Web development environment
Need to create the Video SDK app first? Use Marketplace app management for app creation, manifest validation, app-type quirks, and credential response shapes before generating Video SDK session JWTs.
Need help with OAuth or signatures? See the zoom-oauth skill for authentication flows.
Need pre-join diagnostics on web? Use probe-sdk before Video SDK
join()to reduce first-minute failures.
Start troubleshooting fast: Use the 5-Minute Runbook before deep debugging.
Quick Start (Web)
NPM Usage (Bundler like Vite/Webpack)
What ships with it
60 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.
- android/android.md 1.2 KB
- android/concepts/architecture.md 590 B
- android/concepts/lifecycle-workflow.md 689 B
- android/examples/session-join-pattern.md 660 B
- android/references/android-reference-map.md 496 B
- android/references/environment-variables.md 728 B
- android/references/versioning-and-compatibility.md 680 B
- android/RUNBOOK.md 2.3 KB
- android/scenarios/high-level-scenarios.md 770 B
- android/SKILL.md 1.4 KB
- android/troubleshooting/common-issues.md 630 B
- flutter/concepts/high-level-scenarios.md 641 B
- flutter/concepts/lifecycle-workflow.md 599 B
- flutter/concepts/sdk-architecture-pattern.md 715 B
- flutter/examples/event-handling-pattern.md 1.1 KB
- flutter/examples/session-join-pattern.md 466 B
- flutter/examples/setup-guide.md 2.2 KB
- flutter/references/flutter-reference.md 415 B
- flutter/references/module-map.md 515 B
- flutter/references/official-sources.md 508 B
- flutter/RUNBOOK.md 2.3 KB
- flutter/SKILL.md 3.0 KB
- flutter/troubleshooting/common-issues.md 1.9 KB
- flutter/troubleshooting/deprecated-and-contradictions.md 1.0 KB
- flutter/troubleshooting/version-drift.md 435 B
- ios/concepts/architecture.md 487 B
- ios/concepts/lifecycle-workflow.md 578 B
- ios/examples/session-join-pattern.md 604 B
- ios/ios.md 986 B
- ios/references/environment-variables.md 753 B
- ios/references/ios-reference-map.md 478 B
- ios/references/versioning-and-compatibility.md 643 B
- ios/RUNBOOK.md 2.3 KB
- ios/scenarios/high-level-scenarios.md 756 B
- ios/SKILL.md 1.3 KB
- ios/troubleshooting/common-issues.md 650 B
- linux/concepts/raw-data-vs-canvas.md 17 KB
- linux/concepts/sdk-architecture-pattern.md 15 KB
- linux/concepts/singleton-hierarchy.md 15 KB
- linux/examples/chat.md 215 B
- linux/examples/cloud-recording.md 395 B
- linux/examples/command-channel.md 9.7 KB
- linux/examples/live-streaming.md 234 B
- linux/examples/qt-gtk-integration.md 261 B
- linux/examples/raw-audio-capture.md 215 B
- linux/examples/raw-video-capture.md 251 B
- linux/examples/session-join-pattern.md 21 KB
- linux/examples/transcription.md 255 B
- linux/examples/virtual-audio-video.md 279 B
- linux/linux.md 26 KB
- linux/references/linux-reference.md 27 KB
- linux/RUNBOOK.md 2.2 KB
- linux/SKILL.md 15 KB
- linux/troubleshooting/build-errors.md 2.0 KB
- linux/troubleshooting/common-issues.md 5.3 KB
- linux/troubleshooting/pulseaudio-setup.md 1.7 KB
- linux/troubleshooting/qt-dependencies.md 1.9 KB
- macos/concepts/architecture.md 480 B
- macos/concepts/lifecycle-workflow.md 586 B
- macos/examples/session-join-pattern.md 600 B
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.
- 3d ago First seen · 378 lines · 39 tokens per session scan A acbc1173b155
build-zoom-video-sdk-app is a skill published in the GitHub repository zoom/zoom-plugin (7 stars, last pushed 26d ago), licensed MIT. It adds 39 tokens to every session and 3,381 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…