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 expansion-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/expansion-update)<a href="https://agentmods.dev/skills/anthropics/claude-for-legal/expansion-update"><img src="https://agentmods.dev/badge/skills/anthropics/claude-for-legal/expansion-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/expansion-update"><img src="https://agentmods.dev/badge/skills/anthropics/claude-for-legal/expansion-update.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.00054 | $0.00595 |
| Opus 5 | $0.00027 | $0.00298 |
| Sonnet 5 | $0.00011 | $0.00119 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
expansion-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 13d 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
2 near-identical copies found in the catalogue:
- expansion-update — 89% identical, 4 lines differ
- expansion-update — 89% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/expansion-update
Returns to an open expansion tracker and updates item status based on what has happened since the last session. Recalculates what is now unblocked, flags anything overdue, and surfaces the next priorities.
Instructions
-
Load
~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md. -
Identify the tracker file:
~/.claude/plugins/config/claude-for-legal/employment-legal/expansion-[slug].yaml. If it doesn't exist, respond: "No expansion tracker found for [country]. Run/employment-legal:expansion-kickoff [country]to start one." -
Read the tracker. Show the current state:
[Country] Expansion — last updated [date]
Open: [N] | In progress: [N] | Done: [N] | Blocked: [N]
Next priorities (open items with earliest due dates or highest-dependency):
[item] — owner: [owner]
[item] — owner: [owner]
[item] — owner: [owner]
-
Ask for updates in a single prompt — do not ask about each item one by one:
Which items have moved since we last looked? Tell me what's changed (e.g., "EOR decision made — going with Deel", "outside counsel engaged — call scheduled for Thursday", "PE analysis still open, waiting on tax"). You can also add new items or change due dates.
-
Apply updates to the tracker file. For any item newly marked
done, check whether it unblocks other items and flag those as now actionable. -
If any item has a due date that has passed and is still
openorin-progress, flag it:
⚠️ Overdue: [item] — was due [date], owner: [owner]
- Write the updated tracker. Confirm:
Tracker updated — [N] items closed, [N] still open.
Next priority: [top open item].
Examples
/employment-legal:expansion-update Germany
/employment-legal:expansion-update
(will ask which country if multiple trackers exist)
Detailed tracker schema, item-status rules, and dependency logic live in the
international-expansionreference skill — load it before doing substantive work.
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.
- 13d ago First seen · 75 lines · 54 tokens per session scan A 5c6d2210741a
expansion-update is a skill published in the GitHub repository anthropics/claude-for-legal (9,433 stars, last pushed 21d ago), licensed Apache-2.0. It adds 54 tokens to every session and 595 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.