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 demand-intakegit 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/demand-intake)<a href="https://agentmods.dev/skills/anthropics/claude-for-legal/demand-intake"><img src="https://agentmods.dev/badge/skills/anthropics/claude-for-legal/demand-intake/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/demand-intake"><img src="https://agentmods.dev/badge/skills/anthropics/claude-for-legal/demand-intake.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.00084 | $0.02932 |
| Opus 5.5 | $0.00034 | $0.01173 |
| Sonnet 5 | $0.00017 | $0.00586 |
| Haiku 4.5 | $0.00008 | $0.00293 |
Grade A, and why
demand-intake 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.
How it starts
The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/demand-intake
- Load
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md→ demand-letter practice, landscape, risk calibration. - Follow the workflow and reference below.
- Run the adaptive intake (core 8 always; strategic block if material or
--full). - Generate slug from title + counterparty + year-month.
- Write
~/.claude/plugins/config/claude-for-legal/litigation-legal/demand-letters/[slug]/intake.md. - Confirm with user: "Intake saved. Run
/litigation-legal:demand-draft [slug]when ready."
Demand Intake
Purpose
The drafting is downstream. The value is in the pre-writing — forcing the questions a careless letter skips. Leverage, BATNA, downside tolerance, privilege filters, the actual audience. A demand letter sent without thinking about those is worse than no letter.
Load context
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md→ Demand-letter practice (insurance-tender timing, materiality threshold for matter creation, any seed-doc templates), landscape (counterparty type, repeat-adversary patterns), risk calibration (to pre-estimate materiality), house style. Tone, compliance period, marking, signer are NOT practice-level defaults — they are set per matter in the## Posture for this matterstep below.
Flags
--full→ run the complete intake regardless of materiality heuristics (for counsel who wants thorough every time)
The intake
Posture for this matter (ask FIRST, before the core)
Posture for this matter. Demand-letter tone and terms are case-by-case, not a practice default. Ask:
- Tone: measured / assertive / aggressive? (depends on the relationship, the amount, and whether litigation is likely)
- Response window: what's reasonable given the claim? (14 days is common for payment demands; 30 days for cure; 7 days for cease-and-desist — but the contract or protocol may set it)
- Marking: does this need a "without prejudice" or "without prejudice save as to costs" marking? (settlement communications do; assertions of claim often don't; jurisdiction matters — ask if unsure)
- Signer: you, the client, the GC, instructed solicitor/counsel? Don't assume. Read the prior demand correspondence in the matter file if there is any — it establishes the register.
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 · 272 lines · 84 tokens per session scan A e3e76e58aba2
demand-intake is a skill published in the GitHub repository anthropics/claude-for-legal (9,529 stars, last pushed yesterday), licensed Apache-2.0. It adds 84 tokens to every session and 2,932 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.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
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.
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.
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…
navigate-patent-classification
Traverse IPC/CPC-like classification neighborhoods to expand or delimit a technical patent domain.