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 auto-updatergit 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/auto-updater)<a href="https://agentmods.dev/skills/anthropics/claude-for-legal/auto-updater"><img src="https://agentmods.dev/badge/skills/anthropics/claude-for-legal/auto-updater/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/auto-updater"><img src="https://agentmods.dev/badge/skills/anthropics/claude-for-legal/auto-updater.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
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.00053 | $0.02032 |
| Opus 5.5 | $0.00021 | $0.00813 |
| Sonnet 5.5 | $0.00011 | $0.00406 |
| Haiku 4.5 | $0.00005 | $0.00203 |
Grade B, and why
auto-updater scanned grade B with 1 finding 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
[unified diff — FLAG: hooks can execute arbitrary code] Copies of this mod
1 near-identical copy found in the catalogue:
- auto-updater — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/auto-updater
- Load
~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md→ installed skills + auto-update prefs. - Use the workflow below.
- Check each installed skill's source for newer version.
- Per preference: apply / notify / show diff.
Purpose
Community skills improve. This skill notices when, shows you what changed, and applies updates only with your explicit approval.
Trust posture
Installed skills are code running inside your privileged legal environment. An upstream repository can be compromised, transferred to a new owner, or simply change behavior in ways you don't want. This skill is designed so that no update is ever applied without you reading the diff and approving it. That's not a preference — it's the design.
Load context
~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md → installed skills (with version/commit SHA), update preferences (notify / manual).
Workflow
Step 1: Check each installed skill
For each skill in the installed list:
- Fetch the current commit SHA from the source registry (the exact commit, not a tag or branch head — tags are mutable and can be retroactively rewritten by the publisher; only commit SHAs are immutable)
- Compare to the pinned SHA from install time
- If different: update available
Step 2: Diff and trust review
For each update, show the full diff:
# [skill-name] — [installed SHA] → [latest SHA]
## SKILL.md changes
[unified diff]
## hooks/hooks.json changes
[unified diff — FLAG: hooks can execute arbitrary code]
## .mcp.json changes
[unified diff — FLAG: MCP servers run with your credentials]
## Other files
[list of added/removed/modified files with diffs]
Then run the trust check:
- Did
hooks/hooks.jsonchange? Hooks can execute arbitrary shell commands. Show the diff prominently and ask the user to confirm they understand what the new hooks do. - Did
.mcp.jsonchange? New or changed MCP servers can access your environment. Same treatment. - Did
allowed-toolsortoolsfrontmatter expand? New tool access is a permission escalation. - Any new network calls, file writes outside the skill dir, or command execution in the SKILL.md? Flag them.
- Did the skill's
descriptionor stated purpose change? A skill that claimed to "review NDAs" and now claims to "send contracts" has repurposed itself.
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 · 178 lines · 53 tokens per session scan B e1c1b0953953
auto-updater is a skill published in the GitHub repository anthropics/claude-for-legal (9,810 stars, last pushed 4d ago), licensed Apache-2.0. It adds 53 tokens to every session and 2,032 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-23.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…