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/whiteboardnpx skills add zoom/zoom-plugin --skill whiteboardgit 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/whiteboard)<a href="https://agentmods.dev/skills/zoom/zoom-plugin/whiteboard"><img src="https://agentmods.dev/badge/skills/zoom/zoom-plugin/whiteboard.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.00064 | $0.00926 |
| Opus 5 | $0.00032 | $0.00463 |
| Sonnet 5 | $0.00013 | $0.00185 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
zoom-mcp/whiteboard 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zoom MCP Whiteboard
Dedicated guidance for Zoom's Whiteboard MCP server.
Endpoints
| Transport | URL |
|---|---|
| Streamable HTTP (recommended) | https://mcp.zoom.us/mcp/whiteboard/streamable |
Authentication
- Start app registration from the Whiteboard MCP template.
- User OAuth with Whiteboard scopes is the documented path for Whiteboard MCP execution.
- The bundled connector expects the token in
ZOOM_WHITEBOARD_MCP_ACCESS_TOKEN.
Reference: references/authentication-and-identifiers.md
Required Scopes
Whiteboard MCP tool scopes:
add_a_whiteboard_collaborator→whiteboard:write:collaboratorcreate_a_whiteboard→whiteboard:write:whiteboardcreate_a_whiteboard_by_script→whiteboard:write:whiteboardcreate_a_whiteboard_for_brainstorming→whiteboard:write:whiteboardcreate_a_whiteboard_for_meeting_summary→whiteboard:write:whiteboardcreate_a_whiteboard_for_strategy_analysis→whiteboard:write:whiteboarddelete_a_whiteboard_collaborator→whiteboard:delete:collaboratorget_a_whiteboard→whiteboard:read:whiteboardget_a_whiteboard_collaborator→whiteboard:read:list_collaboratorslist_whiteboards→whiteboard:read:list_whiteboardsupdate_a_whiteboard_collaborator→whiteboard:update:collaborator
Whiteboard ID Mapping
For Whiteboard MCP, use the identifier from the URL segment after /wb/db/, not the numeric
segment after /p/.
Example:
https://us05whiteboard.zoom.us/wb/db/6iktP8hJT3e5qaCuwFuAGg/p/180968285929472
^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^
whiteboard_id page/subresource id
Available Tools
The current Whiteboard MCP tool surface is:
add_a_whiteboard_collaboratorcreate_a_whiteboard_for_brainstorminglist_whiteboardscreate_a_whiteboardget_a_whiteboardget_a_whiteboard_collaboratorcreate_a_whiteboard_by_scriptupdate_a_whiteboard_collaboratordelete_a_whiteboard_collaboratorcreate_a_whiteboard_for_meeting_summarycreate_a_whiteboard_for_strategy_analysis
What ships with it
2 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.
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 · 103 lines · 64 tokens per session scan A d6d0b0d37fa2
zoom-mcp/whiteboard is a skill published in the GitHub repository zoom/zoom-plugin (7 stars, last pushed 27d ago), licensed MIT. It adds 64 tokens to every session and 926 once invoked, about $0.0003 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
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
hallmark
Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots. Use when the user asks to build a new app or landing page, wants to redesign something, invokes Hallmark by name, or uses audit/redesign/study.
read
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.
taiyi-ui-design
TaiyiForge 第 4 阶段 — UI/UX 契约,产出 UI-DESIGN.md。四端通用。.