Claude for Legal is a collection of AI agents, skills, and data connectors for legal work such as commercial, privacy, employment, litigation, regulatory, and intellectual-property matters. Lawyers and legal teams use it through Claude Cowork, Claude Code, or the Claude Managed Agents API, with attorney review required for every output. The catalogue entries are its workflow plugins, skills, agents, and connectors.
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/claude-for-legal --skill matter-updategit clone --depth 1 https://github.com/anthropics/claude-for-legalWrote 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/claude-for-legal/matter-update)<a href="https://agentmods.dev/skills/anthropics/claude-for-legal/matter-update"><img src="https://agentmods.dev/badge/skills/anthropics/claude-for-legal/matter-update/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/claude-for-legal/matter-update"><img src="https://agentmods.dev/badge/skills/anthropics/claude-for-legal/matter-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk 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.00066 | $0.01895 |
| Opus 5.5 | $0.00026 | $0.00758 |
| Sonnet 5 | $0.00013 | $0.00379 |
| Haiku 4.5 | $0.00007 | $0.00189 |
Grade A, and why
matter-update 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- matter-update — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/matter-update
- Follow the workflow and reference below.
- Confirm slug exists in
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/and_log.yaml. - Prompt for event type, date (default today), summary, and any log field updates (risk change, status change, next deadline shift, materiality reclassification).
- Append dated entry to
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md. - Update
_log.yaml— setlast_updatedto today, apply any field updates. - Confirm.
Matter Update
Purpose
The portfolio only stays useful if it stays current. This skill makes logging an update cheap — two minutes of structured capture, no freeform drift.
Load context
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml— find the row~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md— append target~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md— reference (don't rewrite)~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md— risk calibration (if re-assessing risk)
Conflicts gate — unbypassable. Before logging an update, check _log.yaml for the matter slug. If the matter is not in _log.yaml, refuse and route:
"I don't see [matter slug] in the matter log. Run
/litigation-legal:matter-intakefirst so the conflicts check runs and the matter workspace exists. I won't append history to an unmanaged matter — the conflicts check is the gate, and there's nohistory.mdto append to until the matter is intaken."
Input
Slug (required). If not provided, ask — with a short list of recently updated matters to pick from.
The update
1. Event type
Offer categories:
- Procedural — motion filed/received, order issued, hearing held, deadline set
- Discovery — production made/received, depositions taken, subpoena served
- Substantive — new facts, key document surfaced, ruling on merits
- Strategy — posture shift, settlement offer made/received, authority update
- Risk re-assessment — severity or likelihood changed
- Stakeholder — new person looped in, outside counsel change
- Administrative — engagement letter executed, budget adjusted, hold refreshed
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.
- 3d ago First seen · 151 lines · 66 tokens per session scan A 5bfd800c13fa
matter-update is a skill published in the GitHub repository anthropics/claude-for-legal (9,529 stars, last pushed yesterday), licensed Apache-2.0. It adds 66 tokens to every session and 1,895 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-23.
Other skills, from other repositories
vendor-review
Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.
patent-docket
A workflow coordinator for patent case files, from an inventor's technical disclosure to patent application documents. A patent docket is the tracked record of a patent matter, including its stage, questions, drafts, and handoffs.
performance-management
Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.
67-agency-vendor-brief
Dung khi thue NGUOI NGOAI lam — agency, freelancer, production house, vendor: scope of work, spec deliverable, so vong sua, quy trinh duyet, moc thanh toan, dieu khoan IP va bao mat, bang danh gia vendor sau du an. Kich hoat khi user nhac 'brief agency', 'thue freelancer', 'quan ly vendor', 'scope of work', 'agency…
vendor-evaluation
Evaluate, select, and contract with vendors and SaaS tools. Use this skill when comparing alternatives, running an RFP, scoring vendors against criteria, negotiating contracts, planning a switch, or assessing a vendor's risk. Triggers on vendor evaluation, RFP, vendor selection, build vs buy, SaaS evaluation, vendor…
vendor-doc-intake
Daily vendor-onboarding intake for {{requestlabel}}. Validates the W-9, banking form, and signed contract for every new vendor request against a fixed checklist, records every vendor's status in {{vendorregister}}, drafts a follow-up for anything missing or invalid, and posts the batch to {{reviewchannel}}. Load this…