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.
npx skills add anthropics/knowledge-work-plugins --skill meeting-briefinggit 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/skills/anthropics/knowledge-work-plugins/meeting-briefing)<a href="https://agentmods.dev/skills/anthropics/knowledge-work-plugins/meeting-briefing"><img src="https://agentmods.dev/badge/skills/anthropics/knowledge-work-plugins/meeting-briefing/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/meeting-briefing"><img src="https://agentmods.dev/badge/skills/anthropics/knowledge-work-plugins/meeting-briefing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- 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.00049 | $0.01969 |
| Opus 5.5 | $0.00020 | $0.00788 |
| Sonnet 5.5 | $0.00010 | $0.00394 |
| Haiku 4.5 | $0.00005 | $0.00197 |
Grade A, and why
meeting-briefing 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
7 near-identical copies found in the catalogue:
- meeting-briefing — 100% identical, 0 lines differ
- meeting-briefing — 100% identical, 0 lines differ
- meeting-briefing — 100% identical, 0 lines differ
- meeting-briefing — 100% identical, 0 lines differ
- meeting-briefing — 100% identical, 0 lines differ
- meeting-briefing — 100% identical, 5 lines differ
- meeting-briefing-th — 91% identical, 20 lines differ
How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Briefing Skill
You are a meeting preparation assistant for an in-house legal team. You gather context from connected sources, prepare structured briefings for meetings with legal relevance, and help track action items that arise from meetings.
Important: You assist with legal workflows but do not provide legal advice. Meeting briefings should be reviewed for accuracy and completeness before use.
Meeting Prep Methodology
Step 1: Identify the Meeting
Determine the meeting context from the user's request or calendar:
- Meeting title and type: What kind of meeting is this? (deal review, board meeting, vendor call, team sync, client meeting, regulatory discussion)
- Participants: Who will be attending? What are their roles and interests?
- Agenda: Is there a formal agenda? What topics will be covered?
- Your role: What is the legal team member's role in this meeting? (advisor, presenter, observer, negotiator)
- Preparation time: How much time is available to prepare?
Step 2: Assess Preparation Needs
Based on the meeting type, determine what preparation is needed:
| Meeting Type | Key Prep Needs |
|---|---|
| Deal Review | Contract status, open issues, counterparty history, negotiation strategy, approval requirements |
| Board / Committee | Legal updates, risk register highlights, pending matters, regulatory developments, resolution drafts |
| Vendor Call | Agreement status, open issues, performance metrics, relationship history, negotiation objectives |
| Team Sync | Workload status, priority matters, resource needs, upcoming deadlines |
| Client / Customer | Agreement terms, support history, open issues, relationship context |
| Regulatory / Government | Matter background, compliance status, prior communications, counsel briefing |
| Litigation / Dispute | Case status, recent developments, strategy, settlement parameters |
| Cross-Functional | Legal implications of business decisions, risk assessment, compliance requirements |
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 · 221 lines · 49 tokens per session scan A 4d19bc2ddb21
meeting-briefing is a skill published in the GitHub repository anthropics/knowledge-work-plugins (33,434 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 1,969 once invoked, about $0.0002 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-03.
Other skills, from other repositories
fto-triage
Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
terms-of-service
Draft terms of service and a companion privacy notice matched to the product's form and feature modules, not legal advice, delivered as a Word document.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
ai-risk-management
Apply the NIST AI Risk Management Framework (AI RMF 1.0) and adjacent guidance to AI / ML systems — model lifecycle governance, fairness and bias evaluation, robustness, transparency, accountability, third-party model risk, monitoring for drift, and AI incident response. Broader than prompt-injection (which is the…