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/zoom-apps-sdknpx skills add zoom/zoom-plugin --skill zoom-apps-sdkgit clone --depth 1 https://github.com/zoom/zoom-pluginWrote 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.
[](https://agentmods.dev/skills/zoom/zoom-plugin/zoom-apps-sdk)<a href="https://agentmods.dev/skills/zoom/zoom-plugin/zoom-apps-sdk"><img src="https://agentmods.dev/badge/skills/zoom/zoom-plugin/zoom-apps-sdk.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00041 | $0.06420 |
| Opus 5 | $0.00020 | $0.03210 |
| Sonnet 5 | $0.00008 | $0.01284 |
| Haiku 4.5 | $0.00004 | $0.00642 |
Grade A, and why
zoom-apps-sdk 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 4d 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 zoom-apps-sdk — 28 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.
How it starts
The opening of the file, as written. The whole thing — 665 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zoom Apps SDK
Background reference for web apps that run inside the Zoom client. Prefer choose-zoom-approach first, then route here for Layers API, Collaborate Mode, in-client OAuth, and runtime constraints.
Zoom Apps SDK
Build web apps that run inside the Zoom client - meetings, webinars, main client, and Zoom Phone.
Official Documentation: https://developers.zoom.us/docs/zoom-apps/ SDK Reference: https://appssdk.zoom.us/ NPM Package: https://www.npmjs.com/package/@zoom/appssdk
Quick Links
New to Zoom Apps? Follow this path:
- Architecture - Frontend/backend pattern, embedded browser, deep linking
- Quick Start - Complete working Express + SDK app
- Running Contexts - Where your app runs (inMeeting, inMainClient, etc.)
- Zoom Apps vs Meeting SDK - Stop mixing app types
- In-Client OAuth - Seamless authorization with PKCE
- API Reference - 100+ SDK methods
- Integrated Index - see the section below in this file
- 5-Minute Runbook - Preflight checks before deep debugging
Reference:
- API Reference - All SDK methods by category
- Events Reference - All SDK event listeners
- Layers API - Immersive and camera mode rendering
- OAuth Reference - OAuth flows for Zoom Apps
- Zoom Mail - Mail plugin integration
Having issues?
- App won't load in Zoom → Check Domain Allowlist below
- SDK errors → Common Issues
- Local dev setup → Debugging Guide
- Version upgrade → Migration Guide
- Forum-derived FAQs → Forum Top Questions
What ships with it
23 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.
- concepts/architecture.md 7.7 KB
- concepts/meeting-sdk-vs-zoom-apps.md 1.0 KB
- concepts/running-contexts.md 5.6 KB
- concepts/security.md 5.4 KB
- examples/app-communication.md 3.6 KB
- examples/breakout-rooms.md 3.2 KB
- examples/collaborate-mode.md 4.1 KB
- examples/guest-mode.md 3.5 KB
- examples/in-client-oauth.md 6.1 KB
- examples/layers-camera.md 5.7 KB
- examples/layers-immersive.md 7.9 KB
- examples/quick-start.md 7.3 KB
- references/apis.md 5.3 KB
- references/environment-variables.md 1.1 KB
- references/events.md 3.8 KB
- references/layers-api.md 16 KB
- references/oauth.md 5.3 KB
- references/zmail-sdk.md 5.5 KB
- RUNBOOK.md 3.3 KB
- troubleshooting/common-issues.md 4.3 KB
- troubleshooting/debugging.md 3.5 KB
- troubleshooting/forum-top-questions.md 1.1 KB
- troubleshooting/migration.md 3.0 KB
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.
- 4d ago First seen · 665 lines · 41 tokens per session scan A fb29cd1d2aee
zoom-apps-sdk is a skill published in the GitHub repository zoom/zoom-plugin (7 stars, last pushed 28d ago), licensed MIT. It adds 41 tokens to every session and 6,420 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 zoom-apps-sdk, differing in 28 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.
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…