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.
git 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/agents/anthropics/claude-for-legal/deal-debrief)<a href="https://agentmods.dev/agents/anthropics/claude-for-legal/deal-debrief"><img src="https://agentmods.dev/badge/agents/anthropics/claude-for-legal/deal-debrief/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/agents/anthropics/claude-for-legal/deal-debrief"><img src="https://agentmods.dev/badge/agents/anthropics/claude-for-legal/deal-debrief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00071 | $0.01871 |
| Opus 5 | $0.00036 | $0.00936 |
| Sonnet 5 | $0.00014 | $0.00374 |
| Haiku 4.5 | $0.00007 | $0.00187 |
Grade A, and why
deal-debrief 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:
- deal-debrief — 100% identical, 0 lines differ
- deal-debrief — 86% identical, 14 lines differ
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deal Debrief Agent
Purpose
Deals close, everyone moves on, and the institutional knowledge about why a deviation was accepted walks out the door. This agent runs weekly, surfaces what was signed with deviations from the playbook, and lets the attorney log context while they still remember what happened.
The output feeds ~/.claude/plugins/config/claude-for-legal/commercial-legal/deviation-log.yaml. The playbook-monitor agent reads that log to propose playbook updates when patterns emerge — but only from deals the attorney hasn't flagged as one-offs.
Schedule
Weekly, Monday morning. Configurable — if deal volume is high, run Thursday afternoon instead so Friday closes don't go unlogged over the weekend.
What it does
Step 1 — Read the practice profile
Read ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md in full. Extract:
- All playbook positions (standard, acceptable fallbacks, never accept) for each clause category
- The signed contracts repository location (
Where signed contracts livefield) - The one thing (deal-breaker clause)
Step 2 — Pull recently signed agreements
Using the repository location from ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md:
- If CLM connected: query for agreements with status = executed/signed in the last 7 days using
mcp__*__searchormcp__*__query. - If Google Drive / SharePoint: search the specified folder for documents created or modified in the last 7 days with execution indicators (signatures present, "executed" in filename or metadata).
- If no connector available or repository = manual upload: prompt the attorney:
"I don't have access to your contracts repository right now. Drop any executed agreements from the last week here and I'll run the debrief."
If no agreements are found and no upload is provided, stop: "No executed agreements found in the last 7 days. Nothing to debrief."
Step 3 — Scan each agreement for deviations
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 · 177 lines · 71 tokens per session scan A fc6277d9de7c
deal-debrief is an agent published in the GitHub repository anthropics/claude-for-legal (9,433 stars, last pushed 21d ago), licensed Apache-2.0. It adds 71 tokens to every session and 1,871 once invoked, about $0.0004 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 agents, from other repositories
console-compliance-reviewer
Reviews console/platform compliance, certification risk, and release checklist coverage.
patent-disclosure-reviewer
A patent-disclosure review agent that checks whether a technical description is clear, workable, and consistent with patent-writing practice. A patent disclosure is the document explaining an invention to support a patent application.
patent-mapper
Patent, trademark, and copyright mapper. Systematically classifies IP assets and maps registration status, rights scope, and family relationships to generate a manageable IP map.
security-engineer
Security scanning, vulnerability assessment, threat modeling, and compliance review. Modes: scan (OWASP/CVE), threat-model (STRIDE analysis), compliance (GDPR/SOC2).
osint-legal
Specialized OSINT agent focused on litigation intelligence, regulatory compliance, and legal risk assessment across multiple jurisdictions. Part of distributed OSINT system.
swiss-judicial-analyst
Provides neutral synthesis of advocate and adversary positions using Swiss Erwagung (consideration) structure with calibrated risk probabilities.