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 registry-browsergit 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/registry-browser)<a href="https://agentmods.dev/skills/anthropics/claude-for-legal/registry-browser"><img src="https://agentmods.dev/badge/skills/anthropics/claude-for-legal/registry-browser/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/registry-browser"><img src="https://agentmods.dev/badge/skills/anthropics/claude-for-legal/registry-browser.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.00065 | $0.00613 |
| Opus 5.5 | $0.00026 | $0.00245 |
| Sonnet 5.5 | $0.00013 | $0.00123 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
registry-browser 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
1 near-identical copy found in the catalogue:
- registry-browser — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/registry-browser
- Load
~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md→ watched registries. - Use the workflow below.
- Search each registry. Show matches with descriptions.
- Offer to show full SKILL.md for any match.
Purpose
Find skills across the watched registries. Search, preview, decide.
Load context
~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md → watched registries list.
Workflow
Step 1: Fetch registry indexes
For each watched registry:
- GitHub repos: fetch
skills/directory listing and eachSKILL.mdfrontmatter (name + description). - Marketplace-style registries: fetch the index.
Cache the index locally (references/registry-cache.json) so browsing is fast. Refresh cache if >7 days old or on request.
Step 2: Search
Match query against skill names and descriptions. Simple keyword match is fine — these are small enough that fuzzy search is overkill.
Also: browse by category if the registry organizes skills that way.
Step 3: Present matches
## Search: "[query]"
**Found [N] skills across [M] registries:**
### [skill-name]
**From:** [registry name]
**Description:** [from frontmatter]
[View full SKILL.md] [Install]
### [skill-name]
[...]
Step 4: Preview
On "view full SKILL.md": fetch and show the whole file. User reads it before deciding to install. No surprises.
Step 5: Add a registry
If the user has a URL to a registry not in the watchlist:
- Fetch it, validate it's a skills repo (has
skills/or.claude-plugin/) - Show what's in it
- Add to
~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md→ watched registries on confirmation
Default registries
- lpm-skills — 14 legal project management skills. Practice-agnostic. Good starting point.
- Space for others to be added as the ecosystem grows.
What this skill does not do
- Install anything. It browses. skill-installer installs.
- Rate or review skills. It shows you the SKILL.md; you judge.
- Search the whole internet. Only watched registries.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 83 lines · 65 tokens per session scan A 6ea1e14f911f
registry-browser 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 65 tokens to every session and 613 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
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…
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
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.