brief

brief is a skill for Claude Code from anthropics/knowledge-work-plugins. It costs 71 tokens per session (1,424 once invoked), scanned A, original, Apache-2.0.

A legal-work briefing tool that creates daily, topic-specific, or incident-focused summaries from connected email, calendars, contracts, and other internal sources.

In plain words
What is it for?
Use it for morning legal-team updates, research on a legal question, or a rapid summary during a developing incident.
Why use it?
It reduces the time needed to find legally relevant updates and assemble background information. Its results still need review by a qualified legal professional.

Skill for Claude Code ✓ vendor

Written for Claude Code: argument-hint in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md)..

Part of the legal plugin — 9 skills shipped together

Good fit Use it for morning legal-team updates, research on a legal question, or…

Compare 6 skills from other repositories ↓
About the project

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.

anthropics/knowledge-work-plugins · 23,902 stars · on GitHub

Install

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.

Clone the repo
git clone --depth 1 https://github.com/anthropics/knowledge-work-plugins
agentmods
npx agentmods add skills/anthropics/knowledge-work-plugins/brief

Made for: Claude Code.

Or install legal, the plugin that ships this one along with the rest of its 9 skills.

Wrote 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.

agentmods badge for brief

README.md
[![agentmods](https://agentmods.dev/badge/skills/anthropics/knowledge-work-plugins/brief.svg)](https://agentmods.dev/skills/anthropics/knowledge-work-plugins/brief)
Your own site
<a href="https://agentmods.dev/skills/anthropics/knowledge-work-plugins/brief"><img src="https://agentmods.dev/badge/skills/anthropics/knowledge-work-plugins/brief.svg" alt="Measured on agentmods" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,424 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00071 $0.01424
Opus 5 $0.00036 $0.00712
Sonnet 5 $0.00014 $0.00285
Haiku 4.5 $0.00007 $0.00142

Measured 3d ago against content hash 7f1d6d63a74e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

brief 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 3d 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.

Origin

Copies of this mod

3 near-identical copies found in the catalogue:

  • brief — 98% identical, 9 lines differ
  • brief — 91% identical, 7 lines differ
  • brief-th — 86% identical, 12 lines differ
legal/skills/brief/SKILL.md · 209 lines

How it starts

The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Generate contextual briefings for legal work. Supports three modes: daily brief, topic brief, and incident brief.

Important: This command assists with legal workflows but does not provide legal advice. Briefings should be reviewed by qualified legal professionals before being relied upon.

Invocation

/brief daily              # Morning brief of legal-relevant items
/brief topic [query]      # Research brief on a specific legal question
/brief incident [topic]   # Rapid brief on a developing situation

If no mode is specified, ask the user which type of brief they need.

Modes


Daily Brief

A morning summary of everything a legal team member needs to know to start their day.

Sources to Scan

Check each connected source for legal-relevant items:

Email (if connected):

  • New contract requests or review requests
  • Compliance questions or reports
  • Responses from counterparties on active negotiations
  • Flagged or urgent items from the legal team inbox
  • External counsel communications
  • Regulatory or legal update newsletters

Calendar (if connected):

  • Today's meetings that need legal prep (board meetings, deal reviews, vendor calls)
  • Upcoming deadlines this week (contract expirations, filing deadlines, response deadlines)
  • Recurring legal team syncs

Chat (if connected):

  • Overnight messages in legal team channels
  • Direct messages requesting legal input
  • Mentions of legal-relevant topics (contract, compliance, privacy, NDA, terms)
  • Escalations or urgent requests

CLM (if connected):

  • Contracts awaiting review or signature
  • Approaching expiration dates (next 30 days)
  • Newly executed agreements

CRM (if connected):

  • Deals moving to stages that require legal involvement
  • New opportunities flagged for legal review
Output Format
## Daily Legal Brief -- [Date]

### Urgent / Action Required
[Items needing immediate attention, sorted by urgency]

### Contract Pipeline
- **Awaiting Your Review**: [count and list]
- **Pending Counterparty Response**: [count and list]
- **Approaching Deadlines**: [items due this week]

### New Requests
[Contract review requests, NDA requests, compliance questions received since last brief]

### Calendar Today
[Meetings with legal relevance and what prep is needed]

### Team Activity
[Key messages or updates from legal team channels]

### This Week's Deadlines
[Upcoming deadlines and filing dates]

### Sources Not Available
[Any sources that were not connected or returned errors]

Read the full file on GitHub · 209 lines

Changes

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.

  1. 3d ago First seen · 209 lines · 71 tokens per session scan A 7f1d6d63a74e

Subscribe to this mod's changes

brief is a skill published in the GitHub repository anthropics/knowledge-work-plugins (23,902 stars, last pushed yesterday), licensed Apache-2.0. It adds 71 tokens to every session and 1,424 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

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.

wanshuiyin/Auto-claude-code-research-in-sleep · 49 tokens

regulatory-research-fallback

Fallback workflow for regulatory research when web extraction tools fail on government PDFs.

HKUDS/OpenSpace · 20 tokens

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.

x-cmd/x-cmd · 57 tokens

memstack-business-gdpr

Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…

cwinvestments/memstack · 121 tokens

gesellschaftsrechtliche-satzungen-agb

Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.

Klotzkette/claude-fuer-deutsches-recht · 69 tokens

nda-review

Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…

LegalQuants/lq-ai · 79 tokens