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 log-leavegit 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/log-leave)<a href="https://agentmods.dev/skills/anthropics/claude-for-legal/log-leave"><img src="https://agentmods.dev/badge/skills/anthropics/claude-for-legal/log-leave/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/log-leave"><img src="https://agentmods.dev/badge/skills/anthropics/claude-for-legal/log-leave.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 42 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00047 | $0.00612 |
| Opus 5.5 | $0.00019 | $0.00245 |
| Sonnet 5.5 | $0.00009 | $0.00122 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
log-leave 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/log-leave
Adds a new leave entry to ~/.claude/plugins/config/claude-for-legal/employment-legal/leave-register.yaml with the minimum
information needed to start tracking deadlines. Use when an employee goes on
leave and you want the tracker to watch the clocks from day one.
Instructions
-
Read
~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md→ jurisdiction table and Systems section. -
Ask all of the following in a single prompt — do not drip them one at a time:
A few quick questions to set up leave tracking:
- Employee name or role (anonymized is fine)
- Where do they work? (State — this determines which rules apply)
- Leave type: FMLA / state leave (which state) / USERRA / ADA accommodation
- Leave start date
- Is this intermittent leave?
- Expected return date (if known — leave blank if not)
- Has the designation notice been sent? If yes, when?
- Has medical certification been requested? If yes, when?
-
Using the jurisdiction table in
~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md, look up the applicable leave entitlement (hours/weeks) for this leave type in this jurisdiction. -
Compute the first upcoming deadline based on the information provided:
- Designation not yet sent → deadline is 5 business days from leave start
- Med cert requested but not received → deadline is 15 days from request date
- Both sent and received → next deadline is at 75% exhaustion
-
Write a new entry to
~/.claude/plugins/config/claude-for-legal/employment-legal/leave-register.yamlusing the leave register format from the leave-tracker agent. If the file doesn't exist, create it. -
Confirm with a single line:
"Logged. [Employee/Role] — [Leave type] — [Jurisdiction] — started [date]. First deadline: [what it is and when]. Leave tracker will alert automatically."
Examples
/employment-legal:log-leave
/employment-legal:log-leave
Sarah (Sr. Engineer, works in California) just started FMLA today for a
serious health condition. Intermittent. No designation sent yet.
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 · 60 lines · 47 tokens per session scan A 8d2b8a8b92d8
log-leave 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 47 tokens to every session and 612 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.