Knowledge Work Plugins is an open-source collection of Claude extensions organized around roles such as productivity, sales, and customer support. Each plugin combines role-specific guidance, connectors, commands, and sub-agents so knowledge workers can use Claude with their team’s tools and processes. The catalogue entries are examples of, or workflows from, this plugin collection.
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.
git clone --depth 1 https://github.com/anthropics/knowledge-work-pluginsnpx agentmods add skills/anthropics/knowledge-work-plugins/setup-zoom-mcpWrote 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/anthropics/knowledge-work-plugins/setup-zoom-mcp)<a href="https://agentmods.dev/skills/anthropics/knowledge-work-plugins/setup-zoom-mcp"><img src="https://agentmods.dev/badge/skills/anthropics/knowledge-work-plugins/setup-zoom-mcp.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.00046 | $0.00292 |
| Opus 5 | $0.00023 | $0.00146 |
| Sonnet 5 | $0.00009 | $0.00058 |
| Haiku 4.5 | $0.00005 | $0.00029 |
Grade A, and why
setup-zoom-mcp 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 2d 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.
What it actually says
/setup-zoom-mcp
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Plan a Zoom MCP workflow and decide when to use MCP alone versus a hybrid REST API + MCP architecture.
Usage
/setup-zoom-mcp $ARGUMENTS
Workflow
- Determine whether the goal is deterministic automation, AI tool orchestration, or a hybrid.
- If MCP is appropriate, identify the likely Zoom MCP surface and transport assumptions.
- If MCP alone is not enough, define the REST API responsibilities separately.
- Call out auth, scope, and client capability constraints.
- End with a minimal proof-of-concept sequence.
Output
- Recommended MCP strategy
- Connector expectations
- Hybrid boundaries if REST is also required
- Risks and setup notes
- Relevant skill links
Related Skills
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.
- 2d ago First seen · 39 lines · 46 tokens per session scan A a26dd7601ab3
setup-zoom-mcp is a skill published in the GitHub repository anthropics/knowledge-work-plugins (23,902 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 292 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-09-05.
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…
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…
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…