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/probe-sdknpx skills add zoom/zoom-plugin --skill probe-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.00038 | $0.00861 |
| Opus 5 | $0.00019 | $0.00430 |
| Sonnet 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 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.
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
88% identical to probe-sdk — 14 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.
- 3d 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 26d ago), licensed MIT. It adds 38 tokens to every session and 861 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to probe-sdk, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include…
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
playwright
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via playwright-cli or the bundled wrapper script.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.