Reference guidance for Zoom Realtime Media Streams, a service that sends live meeting data to a backend. The data can include audio, video, screen sharing, chat, and transcripts.

Use it when building a backend that handles live Zoom meeting, webinar, Video SDK, or contact-center voice data. It also describes how a separate frontend could display or control that data.

It explains how to receive and process live Zoom streams, including the event that tells a backend streaming can begin.

zoom-rtms — Skill for Claude Code by zoom/zoom-plugin

About the project

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.

zoom/zoom-plugin · 7 stars · on GitHub

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/zoom/zoom-plugin

agentmods

npx agentmods add skills/zoom/zoom-plugin/rtms

Made for: Claude Code.

Or install zoom-plugin, the plugin that ships this one along with the rest of its 47 skills, 7 MCP servers.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/zoom/zoom-plugin/rtms/github.svg)](https://agentmods.dev/skills/zoom/zoom-plugin/rtms)

Your own site

<a href="https://agentmods.dev/skills/zoom/zoom-plugin/rtms"><img src="https://agentmods.dev/badge/skills/zoom/zoom-plugin/rtms/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/zoom/zoom-plugin/rtms"><img src="https://agentmods.dev/badge/skills/zoom/zoom-plugin/rtms.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 5,927 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 95% copy Near-identical to another mod in the catalogue.

Token cost

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.00041	$0.05927
Opus 5.5	$0.00016	$0.02371
Sonnet 5.5	$0.00008	$0.01185
Haiku 4.5	$0.00004	$0.00593

Measured 1mo ago against content hash db5131cbe970, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

zoom-rtms 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.

Origin

This is a copy

95% identical to zoom-rtms — 24 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.

skills/rtms/SKILL.md · 587 lines

How it starts

The opening of the file, as written. The whole thing — 587 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Zoom Realtime Media Streams (RTMS)

Background reference for live Zoom media pipelines. Prefer build-zoom-bot first, then use this skill for stream types, capabilities, and RTMS-specific implementation constraints.

Zoom Realtime Media Streams (RTMS)

Expert guidance for accessing live audio, video, transcript, chat, and screen share data from Zoom meetings, webinars, Video SDK sessions, and Zoom Contact Center Voice in real-time. RTMS uses a WebSocket-based protocol with open standards and does not require a meeting bot to capture the media plane.

Read This First (Critical)

RTMS is primarily a backend media ingestion service.

Your backend receives and processes live media: audio, video, screen share, chat, transcript.
RTMS is not a frontend UI SDK by itself.
Processing is event-triggered: backend waits for RTMS start webhook events before stream handling begins.

Optional architecture (common):

Add a Zoom App SDK frontend for in-client UI/controls.
Stream backend RTMS outputs to frontend via WebSocket (or SSE, gRPC, queue workers, etc.).

Use RTMS for media/data plane, and use frontend frameworks/Zoom Apps for presentation + user interactions.

Official Documentation: https://developers.zoom.us/docs/rtms/ SDK Reference (JS): https://zoom.github.io/rtms/js/ SDK Reference (Python): https://zoom.github.io/rtms/py/ Sample Repository: https://github.com/zoom/rtms-samples

Quick Links

New to RTMS? Follow this path:

Connection Architecture - Two-phase WebSocket design
SDK Quickstart - Fastest way to receive media (recommended)
Manual WebSocket - Full protocol control without SDK
Media Types - Audio, video, transcript, chat, screen share

Complete Implementation:

RTMS Bot - End-to-end bot implementation guide

Reference:

Lifecycle Flow - Complete webhook-to-streaming flow
Data Types - All enums and constants
Webhooks - Event subscription details
Environment Variables - credential modes and runtime knobs
Quickstart Notes - Secondary quickstart guide
Integrated Index - see the section below in this file

Read the full file on GitHub · 587 lines

Files

What ships with it

14 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.

Changes

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 · 587 lines · 41 tokens per session scan A db5131cbe970

Subscribe to this mod's changes

zoom-rtms is a skill published in the GitHub repository zoom/zoom-plugin (7 stars, last pushed 21d ago), licensed MIT. It adds 41 tokens to every session and 5,927 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to zoom-rtms, differing in 24 lines, and is treated as a copy.

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens

zoom-rtms

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

Zoom Realtime Media Streams (RTMS)

Zoom Realtime Media Streams (RTMS)

Read This First (Critical)

Quick Links

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

local-ai-agents

next-cache-components-adoption

chat-pet-sprite-creation

cpu-profile-analysis

insight-error-page

next-cache-components-optimizer