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/call-summaryWrote 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/call-summary)<a href="https://agentmods.dev/skills/anthropics/knowledge-work-plugins/call-summary"><img src="https://agentmods.dev/badge/skills/anthropics/knowledge-work-plugins/call-summary/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.
<a href="https://agentmods.dev/skills/anthropics/knowledge-work-plugins/call-summary"><img src="https://agentmods.dev/badge/skills/anthropics/knowledge-work-plugins/call-summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00065 | $0.01178 |
| Opus 5.5 | $0.00026 | $0.00471 |
| Sonnet 5.5 | $0.00013 | $0.00236 |
| Haiku 4.5 | $0.00006 | $0.00118 |
Grade A, and why
call-summary 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- call-summary — 100% identical, 0 lines differ
- call-summary — 95% identical, 7 lines differ
- call-summary-th — 88% identical, 14 lines differ
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/call-summary
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Process call notes or a transcript to extract action items, draft follow-up communications, and update records.
Usage
/call-summary <notes or transcript>
Process these call notes: $ARGUMENTS
If a file is referenced: @$1
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ CALL SUMMARY │
├─────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ Paste call notes or transcript │
│ ✓ Extract key discussion points and decisions │
│ ✓ Identify action items with owners and due dates │
│ ✓ Surface objections, concerns, and open questions │
│ ✓ Draft customer-facing follow-up email │
│ ✓ Generate internal summary for your team │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + Transcripts: Pull recording automatically (e.g. Gong, Fireflies) │
│ + CRM: Update opportunity, log activity, create tasks │
│ + Email: Send follow-up directly from draft │
│ + Calendar: Link to meeting, pull attendee context │
└─────────────────────────────────────────────────────────────────┘
What I Need From You
Option 1: Paste your notes Just paste whatever you have — bullet points, rough notes, stream of consciousness. I'll structure it.
Option 2: Paste a transcript If you have a full transcript from your video conferencing tool (e.g. Zoom, Teams) or conversation intelligence tool (e.g. Gong, Fireflies), paste it. I'll extract the key moments.
Option 3: Describe the call Tell me what happened: "Had a discovery call with Acme Corp. Met with their VP Eng and CTO. They're evaluating us vs Competitor X. Main concern is integration timeline."
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 · 169 lines · 65 tokens per session scan A 8aefb4bc513e
call-summary is a skill published in the GitHub repository anthropics/knowledge-work-plugins (31,573 stars, last pushed yesterday), licensed Apache-2.0. It adds 65 tokens to every session and 1,178 once invoked, about $0.0003 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…