legal-response

legal-response is a skill for Claude Code from anthropics/knowledge-work-plugins. It costs 56 tokens per session (3,355 once invoked), scanned A, original, Apache-2.0.

A template-based tool for drafting replies to common legal inquiries, including data-subject requests, litigation holds, vendor questions, NDA requests, subpoenas, and insurance claims.

In plain words
What is it for?
Use it to prepare responses to privacy requests, legal notices, business-team NDA requests, vendor questions, and other listed inquiries.
Why use it?
It speeds up routine legal correspondence while identifying situations that should not receive a standard reply. Generated responses should be reviewed before sending.

Skill for Claude Code ✓ vendor

Written for Claude Code: argument-hint in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md)..

Part of the legal plugin — 9 skills shipped together

Good fit Use it to prepare responses to privacy requests, legal notices, business-team NDA…

Compare 6 skills from other repositories ↓
About the project

Knowledge Work Plugins is an open-source collection of Claude extensions organized around roles such as productivity, sales, and customer support. Each plugin combines role-specific guidance, connectors, commands, and sub-agents so knowledge workers can use Claude with their team’s tools and processes. The catalogue entries are examples of, or workflows from, this plugin collection.

anthropics/knowledge-work-plugins · 23,902 stars · on GitHub

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/anthropics/knowledge-work-plugins
agentmods
npx agentmods add skills/anthropics/knowledge-work-plugins/legal-response

Made for: Claude Code.

Or install legal, the plugin that ships this one along with the rest of its 9 skills.

Wrote 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.

agentmods badge for legal-response

README.md
[![agentmods](https://agentmods.dev/badge/skills/anthropics/knowledge-work-plugins/legal-response.svg)](https://agentmods.dev/skills/anthropics/knowledge-work-plugins/legal-response)
Your own site
<a href="https://agentmods.dev/skills/anthropics/knowledge-work-plugins/legal-response"><img src="https://agentmods.dev/badge/skills/anthropics/knowledge-work-plugins/legal-response.svg" alt="Measured on agentmods" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,355 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00056 $0.03355
Opus 5 $0.00028 $0.01677
Sonnet 5 $0.00011 $0.00671
Haiku 4.5 $0.00006 $0.00335

Measured 3d ago against content hash b3a0585ee00a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

legal-response 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

legal/skills/legal-response/SKILL.md · 458 lines

How it starts

The opening of the file, as written. The whole thing — 458 lines — stays where its author put it; the contents beside it link to each section on GitHub.

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Generate a response to a common legal inquiry using configured templates. Customizes the response with specific details and includes escalation triggers for situations that should not use a templated response.

Important: This command assists with legal workflows but does not provide legal advice. Generated responses should be reviewed by qualified legal professionals before being sent, especially for regulated communications.

Invocation

/legal-response [inquiry-type]

Common inquiry types:

  • dsr or data-subject-request -- Data subject access/deletion/correction requests
  • hold or discovery-hold -- Litigation hold notices
  • vendor or vendor-question -- Vendor legal questions
  • nda or nda-request -- NDA requests from business teams
  • privacy or privacy-inquiry -- Privacy-related questions
  • subpoena -- Subpoena or legal process responses
  • insurance -- Insurance claim notifications
  • custom -- Use a custom template

If no inquiry type is provided, ask the user what type of response they need and show available categories.

Workflow

Step 1: Identify Inquiry Type

Accept the inquiry type from the user. If the type is ambiguous, show available categories and ask for clarification.

Step 2: Load Template

Look for templates in local settings (e.g., legal.local.md or a templates directory).

If templates are configured:

  • Load the appropriate template for the inquiry type
  • Identify required variables (recipient name, dates, specific details)

If no templates are configured:

  • Inform the user that no templates were found for this inquiry type
  • Offer to help create a template (see Template Creation Guide below)
  • Provide a reasonable default response structure based on the inquiry type

Step 3: Check Escalation Triggers

Before generating any response, evaluate whether this situation has characteristics that should NOT use a templated response.

Read the full file on GitHub · 458 lines

Changes

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.

  1. 3d ago First seen · 458 lines · 56 tokens per session scan A b3a0585ee00a

Subscribe to this mod's changes

legal-response is a skill published in the GitHub repository anthropics/knowledge-work-plugins (23,902 stars, last pushed yesterday), licensed Apache-2.0. It adds 56 tokens to every session and 3,355 once invoked, about $0.0003 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-09-03.

Related

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.

wanshuiyin/Auto-claude-code-research-in-sleep · 49 tokens

regulatory-research-fallback

Fallback workflow for regulatory research when web extraction tools fail on government PDFs.

HKUDS/OpenSpace · 20 tokens

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.

x-cmd/x-cmd · 57 tokens

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…

cwinvestments/memstack · 121 tokens

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.

Klotzkette/claude-fuer-deutsches-recht · 69 tokens

nda-review

Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…

LegalQuants/lq-ai · 79 tokens