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/team-chatnpx skills add zoom/zoom-plugin --skill team-chatgit 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.00045 | $0.05962 |
| Opus 5 | $0.00023 | $0.02981 |
| Sonnet 5 | $0.00009 | $0.01192 |
| Haiku 4.5 | $0.00005 | $0.00596 |
Grade B, and why
build-zoom-team-chat-app scanned grade B with 1 finding 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
const response = await fetch('https://api.zoom.us/v2/chat/users/me/messages', { method: 'POST', This is a copy
91% identical to zoom-team-chat — 97 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 — 727 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/build-zoom-team-chat-app
Background reference for Zoom Team Chat integrations. Use this after the workflow is clear, especially when the Team Chat API versus Chatbot API distinction matters.
For agent-driven MCP tooling that sends or edits messages, manages Team Chat channels, or adds channel members through Zoom's hosted MCP server, use ../zoom-mcp/team-chat/SKILL.md. Keep this skill as the default for deterministic REST API implementation, chatbot apps, webhooks, retry logic, and production backend control.
Read This First (Critical)
There are two different integration types and they are not interchangeable:
-
Team Chat API (user type)
- Sends messages as a real authenticated user
- Uses User OAuth (
authorization_code) - Endpoint family:
/v2/chat/users/...
-
Chatbot API (bot type)
- Sends messages as your bot identity
- Uses Client Credentials (
client_credentials) - Endpoint family:
/v2/im/chat/messages
If you choose the wrong type early, auth/scopes/endpoints all mismatch and implementation fails.
Official Documentation: https://developers.zoom.us/docs/team-chat/
Chatbot Documentation: https://developers.zoom.us/docs/team-chat/chatbot/extend/
API Reference: https://developers.zoom.us/docs/api/rest/reference/chatbot/
Quick Links
New to Team Chat? Follow this path:
- Get Started - End-to-end fast path (user type vs bot type)
- Choose Your API - Team Chat API vs Chatbot API
- Environment Setup - Credentials, scopes, app configuration
- OAuth Setup - Complete authentication flow
- Send First Message - Working code to send messages
Reference:
- Chatbot Message Cards - Complete card component reference
- Webhook Events - All webhook event types
- API Reference - Endpoints, methods, parameters
- Sample Applications - 10+ official sample apps
- Integrated Index - see the section below in this file
What ships with it
37 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/api-selection.md 7.9 KB
- concepts/authentication.md 1.7 KB
- concepts/deployment.md 719 B
- concepts/environment-setup.md 8.8 KB
- concepts/message-structure.md 676 B
- concepts/security.md 479 B
- concepts/webhooks.md 12 KB
- examples/button-actions.md 394 B
- examples/channel-management.md 321 B
- examples/chatbot-setup.md 14 KB
- examples/database-integration.md 313 B
- examples/dropdown-selects.md 305 B
- examples/form-submissions.md 386 B
- examples/llm-integration.md 532 B
- examples/multi-step-workflows.md 301 B
- examples/oauth-setup.md 1.6 KB
- examples/scheduled-alerts.md 353 B
- examples/send-message.md 418 B
- examples/slash-commands.md 510 B
- examples/token-management.md 443 B
- get-started.md 1.9 KB
- references/api-reference.md 918 B
- references/environment-variables.md 1.3 KB
- references/error-codes.md 1005 B
- references/jid-formats.md 248 B
- references/message-cards.md 6.6 KB
- references/rate-limits.md 206 B
- references/sample-comparison.md 1.1 KB
- references/samples.md 15 KB
- references/scopes.md 341 B
- references/webhook-events.md 565 B
- RUNBOOK.md 3.1 KB
- troubleshooting/common-issues.md 11 KB
- troubleshooting/deployment-issues.md 641 B
- troubleshooting/message-issues.md 542 B
- troubleshooting/oauth-issues.md 882 B
- troubleshooting/webhook-issues.md 365 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.
- 3d ago First seen · 727 lines · 45 tokens per session scan B c48593c09eae
build-zoom-team-chat-app is a skill published in the GitHub repository zoom/zoom-plugin (7 stars, last pushed 26d ago), licensed MIT. It adds 45 tokens to every session and 5,962 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (sends data to an external url). It is 91% identical to zoom-team-chat, differing in 97 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…