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/skills/macosnpx skills add zoom/skills --skill macosgit clone --depth 1 https://github.com/zoom/skillsWrote 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/skills/macos)<a href="https://agentmods.dev/skills/zoom/skills/macos"><img src="https://agentmods.dev/badge/skills/zoom/skills/macos.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.00048 | $0.00370 |
| Opus 5 | $0.00024 | $0.00185 |
| Sonnet 5 | $0.00010 | $0.00074 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
zoom-meeting-sdk-macos 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- zoom-meeting-sdk-macos — 91% identical, 3 lines differ
What it actually says
Zoom Meeting SDK (macOS)
Use this skill when building macOS apps with embedded Zoom meeting capabilities.
Start Here
- macos.md
- concepts/lifecycle-workflow.md
- concepts/architecture.md
- examples/join-start-pattern.md
- scenarios/high-level-scenarios.md
- references/macos-reference-map.md
- references/environment-variables.md
- references/versioning-and-compatibility.md
- troubleshooting/common-issues.md
Key Sources
- Docs: https://developers.zoom.us/docs/meeting-sdk/macos/
- API reference: https://marketplacefront.zoom.us/sdk/meeting/macos/annotated.html
- Parent skill: ../SKILL.md
Operations
- RUNBOOK.md - 5-minute preflight and debugging checklist.
What ships with it
10 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 719 B
- concepts/lifecycle-workflow.md 489 B
- examples/join-start-pattern.md 584 B
- macos.md 708 B
- references/environment-variables.md 894 B
- references/macos-reference-map.md 790 B
- references/versioning-and-compatibility.md 1.1 KB
- RUNBOOK.md 2.3 KB
- scenarios/high-level-scenarios.md 624 B
- troubleshooting/common-issues.md 726 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.
- 4d ago First seen · 41 lines · 48 tokens per session scan A b5173aa5fa15
zoom-meeting-sdk-macos is a skill published in the GitHub repository zoom/skills (71 stars, last pushed 7d ago), licensed MIT. It adds 48 tokens to every session and 370 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. 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…