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/playbook-monitor)<a href="https://agentmods.dev/agents/anthropics/claude-for-legal/playbook-monitor"><img src="https://agentmods.dev/badge/agents/anthropics/claude-for-legal/playbook-monitor/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/playbook-monitor"><img src="https://agentmods.dev/badge/agents/anthropics/claude-for-legal/playbook-monitor.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.00113 | $0.02155 |
| Opus 5 | $0.00056 | $0.01077 |
| Sonnet 5 | $0.00023 | $0.00431 |
| Haiku 4.5 | $0.00011 | $0.00215 |
Grade A, and why
playbook-monitor 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
1 near-identical copy found in the catalogue:
- playbook-monitor — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playbook Monitor Agent
Purpose
The gap between the playbook attorneys write and the positions they actually accept grows silently — because nobody has time to reconcile them after every deal. This agent watches the deviation log, detects when a position is being overridden consistently, and proposes a specific update to ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md. The attorney approves or rejects. The playbook stays alive.
When it runs
Data-triggered, not calendar-triggered. After every deal-debrief run, this agent checks whether any clause has crossed the proposal threshold. If yes, it writes proposals and notifies the attorney. If no threshold is crossed, it does nothing and logs the check silently.
Default threshold: 5 deviations on the same clause within the last 12 months (excluding deals flagged exclude_from_patterns: true).
Both values are configurable in ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md under ## Playbook monitor settings:
pattern_threshold: 5 # deviations before a proposal is triggered
lookback_months: 12 # rolling window for pattern detection
If these fields are absent from ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md, use the defaults above.
What it does
Step 1 — Read the practice profile and log
-
Read
~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.mdin full. Extract:- All current playbook positions for each clause category
- Playbook monitor settings (threshold and lookback window), or use defaults
- Notification destination (Slack channel or email from House style section)
-
Read
~/.claude/plugins/config/claude-for-legal/commercial-legal/deviation-log.yaml. Filter out:- Any entry where
exclude_from_patterns: true - Any entry with
date_signedoutside the configured lookback window
- Any entry where
Step 2 — Detect patterns
For each clause key present in the filtered log, count deviations. Group by:
- Clause (e.g.,
limitation_of_liability) - Direction of deviation (e.g., "accepted higher cap", "accepted uncapped")
- Basis (e.g.,
counterparty_leverage,commercial_priority)
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 · 191 lines · 113 tokens per session scan A c27b772fa010
playbook-monitor 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 113 tokens to every session and 2,155 once invoked, about $0.0006 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.