A command that drafts responses to common legal inquiries from configured templates. It covers requests such as data access, litigation holds, vendor questions, privacy inquiries, and subpoenas, but is not legal advice.

Use it to prepare a draft response for a supported inquiry type, then have a legal professional review it before sending.

It reduces the time spent starting routine legal replies while identifying cases that need review or escalation by a qualified lawyer.

respond — Command for Claude Code by Kromer-Group

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/Kromer-Group/Claude-Legal

agentmods

npx agentmods add commands/kromer-group/claude-legal/respond

Made for: Claude Code.

Or install legal, the plugin that ships this one along with the rest of its 6 skills, 5 commands, 5 MCP servers.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/kromer-group/claude-legal/respond/github.svg)](https://agentmods.dev/commands/kromer-group/claude-legal/respond)

Your own site

<a href="https://agentmods.dev/commands/kromer-group/claude-legal/respond"><img src="https://agentmods.dev/badge/commands/kromer-group/claude-legal/respond/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/kromer-group/claude-legal/respond"><img src="https://agentmods.dev/badge/commands/kromer-group/claude-legal/respond.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,449 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.

Model	Per session	Once invoked
Fable 5.1	$0.00011	$0.01449
Opus 5	$0.00005	$0.00724
Sonnet 5	$0.00002	$0.00290
Haiku 4.5	$0.00001	$0.00145

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

Security

Grade A, and why

respond 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 11d 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

1 near-identical copy found in the catalogue:

respond — 100% identical, 0 lines differ

commands/respond.md · 198 lines

How it starts

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

/respond -- Generate Response from Templates

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.

Invocation

/respond [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 Step 6)
Provide a reasonable default response structure based on the inquiry type

Step 3: Check Escalation Triggers

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

Read the full file on GitHub · 198 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.

11d ago First seen · 198 lines · 11 tokens per session scan A 319c785cdee1

Subscribe to this mod's changes

respond is a command published in the GitHub repository Kromer-Group/Claude-Legal (11 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,449 once invoked, about $0.0001 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.

Legal and compliance

deps-audit

Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.

wshobson/agents · 23 tokens

review-epo-claims

Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.

RobThePCGuy/Claude-Patent-Creator · 22 tokens

voice-compliance

Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.

avelikiy/great_cto · 53 tokens

review-policy

Review a policy document for structure, coverage, and language quality.

mlunato47/claude-grc-plugin · 12 tokens

at-dsgvo

You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…

tractorjuice/arc-kit · 35 tokens

au-pspf

You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.

tractorjuice/arc-kit · 33 tokens