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/contact-centernpx skills add zoom/zoom-plugin --skill contact-centergit 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/contact-center)<a href="https://agentmods.dev/skills/zoom/zoom-plugin/contact-center"><img src="https://agentmods.dev/badge/skills/zoom/zoom-plugin/contact-center.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.1 | $0.00048 | $0.01372 |
| Opus 5 | $0.00024 | $0.00686 |
| Sonnet 5 | $0.00010 | $0.00274 |
| Haiku 4.5 | $0.00005 | $0.00137 |
Grade A, and why
build-zoom-contact-center-app 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 6d 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
86% identical to build-zoom-contact-center-app — 8 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/build-zoom-contact-center-app
Background reference for Zoom Contact Center integrations across app, web, and native mobile surfaces.
Implementation guidance for Zoom Contact Center across:
- Contact Center apps in the Zoom client (Zoom Apps SDK path)
- Web channel embeds (chat/video/campaign)
- Native mobile SDKs (Android/iOS)
Official docs:
- https://developers.zoom.us/docs/contact-center/
- https://developers.zoom.us/docs/contact-center/web/sdk-reference/
- https://marketplacefront.zoom.us/sdk/contact/android/index.html
- https://marketplacefront.zoom.us/sdk/contact/ios/index.html
Routing Guardrail
- If the user is building an app inside the Zoom Contact Center desktop client, stay on the Zoom Apps SDK path and use this skill plus
zoom-apps-sdk. - If the user is embedding chat/video widgets on a website, route to web/SKILL.md.
- If the user is integrating native Android or iOS SDK binaries, route to android/SKILL.md or ios/SKILL.md.
- If the user needs Contact Center call-control or queue APIs, chain with ../rest-api/SKILL.md.
Quick Links
Start here:
- concepts/architecture-and-lifecycle.md
- scenarios/high-level-scenarios.md
- references/forum-top-questions.md
- references/versioning-and-compatibility.md
- references/samples-validation.md
- references/environment-variables.md
- troubleshooting/common-drift-and-breaks.md
- RUNBOOK.md
Platform skills:
Documentation Structure
contact-center/
├── SKILL.md
├── RUNBOOK.md
├── concepts/
│ └── architecture-and-lifecycle.md
├── scenarios/
│ └── high-level-scenarios.md
├── references/
│ ├── versioning-and-compatibility.md
│ ├── samples-validation.md
│ └── environment-variables.md
├── troubleshooting/
│ └── common-drift-and-breaks.md
├── android/
│ ├── SKILL.md
│ ├── concepts/sdk-lifecycle.md
│ ├── examples/service-patterns.md
│ ├── references/android-reference-map.md
│ └── troubleshooting/common-issues.md
├── ios/
│ ├── SKILL.md
│ ├── concepts/sdk-lifecycle.md
│ ├── examples/service-patterns.md
│ ├── references/ios-reference-map.md
│ └── troubleshooting/common-issues.md
└── web/
├── SKILL.md
├── concepts/lifecycle-and-events.md
├── examples/app-context-and-state.md
├── references/web-reference-map.md
└── troubleshooting/common-issues.md
What ships with it
26 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.
- android/concepts/sdk-lifecycle.md 1019 B
- android/examples/service-patterns.md 1.7 KB
- android/references/android-reference-map.md 1.0 KB
- android/RUNBOOK.md 2.3 KB
- android/SKILL.md 1.7 KB
- android/troubleshooting/common-issues.md 834 B
- concepts/architecture-and-lifecycle.md 1.9 KB
- ios/concepts/sdk-lifecycle.md 1.2 KB
- ios/examples/service-patterns.md 1.6 KB
- ios/references/ios-reference-map.md 884 B
- ios/RUNBOOK.md 2.2 KB
- ios/SKILL.md 1.6 KB
- ios/troubleshooting/common-issues.md 980 B
- references/environment-variables.md 1.7 KB
- references/forum-top-questions.md 3.2 KB
- references/samples-validation.md 1.7 KB
- references/versioning-and-compatibility.md 1.2 KB
- RUNBOOK.md 3.0 KB
- scenarios/high-level-scenarios.md 1.7 KB
- troubleshooting/common-drift-and-breaks.md 1.6 KB
- web/concepts/lifecycle-and-events.md 1.0 KB
- web/examples/app-context-and-state.md 1.5 KB
- web/references/web-reference-map.md 1.2 KB
- web/RUNBOOK.md 2.2 KB
- web/SKILL.md 1.7 KB
- web/troubleshooting/common-issues.md 862 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.
- 6d ago First seen · 130 lines · 48 tokens per session scan A f067f0caff13
build-zoom-contact-center-app is a skill published in the GitHub repository zoom/zoom-plugin (7 stars, last pushed 29d ago), licensed MIT. It adds 48 tokens to every session and 1,372 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to build-zoom-contact-center-app, differing in 8 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.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…