Zoom Plugin is a Claude plugin that helps plan, build, and debug Zoom integrations across APIs, SDKs, webhooks, bots, and MCP connections. It is for developers creating Zoom applications, with catalogue entries providing guidance, workflows, and MCP connectors for selecting and implementing the relevant Zoom products.
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 skills add zoom/zoom-plugin --skill probe-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/probe-sdk)<a href="https://agentmods.dev/skills/zoom/zoom-plugin/probe-sdk"><img src="https://agentmods.dev/badge/skills/zoom/zoom-plugin/probe-sdk/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.
<a href="https://agentmods.dev/skills/zoom/zoom-plugin/probe-sdk"><img src="https://agentmods.dev/badge/skills/zoom/zoom-plugin/probe-sdk.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00038 | $0.00861 |
| Opus 5.5 | $0.00015 | $0.00344 |
| Sonnet 5.5 | $0.00008 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
probe-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 1mo 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
100% identical to probe-sdk — 0 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zoom Probe SDK
Background reference for preflight diagnostics on user devices and networks before meeting or session workflows.
Official docs:
Reference sample:
Routing Guardrail
- Use Probe SDK when the user needs client-side diagnostics and readiness scoring (device/network/browser capability), not meeting/session join.
- If user needs embedded meeting flows, route to ../meeting-sdk/SKILL.md.
- If user needs custom real-time session UX, route to ../video-sdk/SKILL.md.
- If user needs backend orchestration of events/APIs, chain with ../rivet-sdk/SKILL.md, ../oauth/SKILL.md, and ../rest-api/SKILL.md.
Quick Links
Start here:
- probe-sdk.md
- concepts/architecture-and-lifecycle.md
- scenarios/high-level-scenarios.md
- examples/diagnostic-page-pattern.md
- examples/comprehensive-network-pattern.md
- references/probe-reference-map.md
- references/environment-variables.md
- references/versioning-and-compatibility.md
- references/samples-validation.md
- references/source-map.md
- troubleshooting/common-issues.md
- RUNBOOK.md
Common Lifecycle Pattern
- Initialize
Prober/Reporter. - Request media permissions and enumerate devices.
- Run targeted diagnostics (
diagnoseAudio,diagnoseVideo). - Run comprehensive network diagnostic (
startToDiagnose) and stream stats to UI. - Produce final report and apply readiness gates.
- Stop/cleanup (
stopToDiagnose,stopToDiagnoseVideo,releaseMediaStream,cleanup).
What ships with it
12 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-and-lifecycle.md 1.9 KB
- examples/comprehensive-network-pattern.md 904 B
- examples/diagnostic-page-pattern.md 1.4 KB
- probe-sdk.md 698 B
- references/environment-variables.md 1.3 KB
- references/probe-reference-map.md 967 B
- references/samples-validation.md 1005 B
- references/source-map.md 502 B
- references/versioning-and-compatibility.md 1.1 KB
- RUNBOOK.md 2.4 KB
- scenarios/high-level-scenarios.md 1.2 KB
- troubleshooting/common-issues.md 1.9 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.
- 1mo ago First seen · 82 lines · 38 tokens per session scan A a2cbce7b0f77
probe-sdk is a skill published in the GitHub repository zoom/zoom-plugin (7 stars, last pushed 21d ago), licensed MIT. It adds 38 tokens to every session and 861 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to probe-sdk, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
experimental-read-code-coverage-metrics
Retrieves and analyzes Chromium per-CL code coverage data from the Findit API. Records per-CL coverage metrics for all modified source files and extracts unexecuted code lines.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…