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
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.
git clone --depth 1 https://github.com/anthropics/knowledge-work-pluginsWrote 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/commands/anthropics/knowledge-work-plugins/standup)<a href="https://agentmods.dev/commands/anthropics/knowledge-work-plugins/standup"><img src="https://agentmods.dev/badge/commands/anthropics/knowledge-work-plugins/standup.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.00011 | $0.00303 |
| Opus 5 | $0.00005 | $0.00151 |
| Sonnet 5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
standup 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- standup — 100% identical, 11 lines differ
What it actually says
-
Use
slack_read_user_profile(with no user_id) to get the current user's profile information, including their user ID and display name. -
Search for the user's recent messages using
slack_search_publicwith the filterfrom:<@USER_ID>andafter:set to yesterday's date. This captures messages from the last working day. -
Review the messages found and categorize them into standup themes:
- What I worked on — Topics, projects, or tasks the user discussed or contributed to
- What I'm working on next — Any mentions of upcoming work, plans, or follow-ups
- Blockers — Any questions asked that went unanswered, issues raised, or explicit mentions of being stuck
-
For messages in threads, use
slack_read_threadto get the full context so you can accurately describe what the user contributed. -
Format the standup as:
*Standup for <display name> — <today's date>* *Done:* - Item 1 - Item 2 *Doing:* - Item 1 *Blockers:* - None / Item 1 -
Present the standup to the user for review. They can edit, adjust, or ask you to post it to a specific channel.
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 · 32 lines · 11 tokens per session scan A 2d6db206f936
standup is a command published in the GitHub repository anthropics/knowledge-work-plugins (23,911 stars, last pushed 2d ago), licensed Apache-2.0. It adds 11 tokens to every session and 303 once invoked, about $0.0001 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-03.
Other commands, from other repositories
standup
Quick daily standup from today's Claude Code sessions — grouped by project, with cost and errors.
fire-todos
Capture, list, and manage todos during work sessions.
gsd:resume-work
Resume work from previous session with full context restoration.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
ops
Weekly operations loop — triage the inquiry inbox, advance the CRM pipeline, sweep open PRs across repos, and surface the content plan. Loads the ops skill.
standup
A command that creates a daily stand-up report by summarizing recent work, planned tasks, calendar events, and blockers.