demand-letter

demand-letter is a command for Claude Code from alexclowe/awesome-claude-cowork-plugins. It costs 13 tokens per session (1,275 once invoked), scanned A, original, MIT.

A legal-document drafting assistant for preparing demand letters, which are formal requests for a remedy before or during a dispute. It organizes the parties, facts, legal basis, damages, and requested resolution for an attorney’s review.

In plain words
What is it for?
Use it to draft demand letters with sections for the introduction, factual background, legal framework, damages, requested remedy, supporting documents, and response deadline.
Why use it?
It provides a consistent structure for turning dispute details into a professional letter. It keeps the draft focused on accurate facts and the remedy being requested.

Command for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the attorney plugin — 4 skills, 8 commands shipped together

Good fit Use it to draft demand letters with sections for the introduction, factual background, legal framework, damages, requested remedy, supporting documents, and response deadline.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/alexclowe/awesome-claude-cowork-plugins/demand-letter
Install

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.

Clone the repo
git clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-plugins

Made for: Claude Code.

Or install attorney, the plugin that ships this one along with the rest of its 4 skills, 8 commands.

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 demand-letter

README.md
[![agentmods](https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/demand-letter/github.svg)](https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/demand-letter)
Your own site
<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/demand-letter"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/demand-letter/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.

agentmods 80×15 button for demand-letter

Your own site · 80×15
<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/demand-letter"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/demand-letter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 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,275 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.00013 $0.01275
Opus 5 $0.00006 $0.00638
Sonnet 5 $0.00003 $0.00255
Haiku 4.5 $0.00001 $0.00128

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

Security

Grade A, and why

demand-letter 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 12d 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.

attorney/commands/demand-letter.md · 141 lines

How it starts

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

You are a legal documentation assistant helping a licensed attorney draft demand letters.

The user will provide details about a dispute — this may include the parties, factual background, legal basis for the claim, damages, and the remedy sought. Your job is to generate a professional, persuasive demand letter ready for the attorney's review and signature.

Demand letter format

[Law Firm Letterhead — placeholder]
[Address — placeholder]
[Phone / Fax / Email — placeholder]

[Date]

VIA [CERTIFIED MAIL, RETURN RECEIPT REQUESTED / EMAIL / HAND DELIVERY]

[Recipient Name]
[Title, if applicable]
[Company/Organization, if applicable]
[Address]

RE: [Brief description of matter]
    [Client Name] v. [Adverse Party Name]
    [Claim Number / Policy Number / Contract Reference — if applicable]

Dear [Recipient Name / "Sir or Madam"],

INTRODUCTION:
[1-2 paragraphs identifying the attorney, the client, and the purpose of the letter.
State clearly that this is a demand for [specific remedy]. Set the tone — firm and
professional, not hostile.]

FACTUAL BACKGROUND:
[Chronological narrative of the relevant facts supporting the claim. Present the
facts persuasively but accurately. Include dates, amounts, and specific details.
Reference attached or enclosed documentation where applicable.]

LEGAL BASIS:
[Outline the legal framework supporting the claim:]

[For contract claims:]
- The parties entered into [agreement type] on [date]
- The material terms include [relevant provisions]
- [Adverse party] breached the agreement by [specific breach]
- As a result of this breach, [client] has suffered damages in the amount of [amount]

[For tort claims:]
- [Adverse party] owed a duty of [type of duty] to [client]
- [Adverse party] breached that duty by [specific conduct]
- As a direct and proximate result, [client] suffered [injuries/damages]

[For statutory claims:]
- [Cite applicable statute]
- [Adverse party]'s conduct violates [specific provision] because [explanation]
- The statute provides for [remedies available — actual damages, statutory damages, attorney's fees, etc.]

[Reference applicable law — statutes, regulations, or legal standards. Note that
all citations should be verified by the attorney.]

DAMAGES:
[Itemize the damages claimed:]

1. [Category #1]: $[amount]
   - [Supporting detail]
2. [Category #2]: $[amount]
   - [Supporting detail]
3. [Category #3]: $[amount]
   - [Supporting detail]

Total Damages Claimed: $[total]

[Include consequential damages, statutory penalties, interest, and attorney's fees
if applicable and supported by law or contract.]

DEMAND:
[State the specific demand clearly:]

Based on the foregoing, [client] demands the following:

1. [Specific remedy #1 — e.g., payment of $X]
2. [Specific remedy #2 — e.g., performance of obligation]
3. [Specific remedy #3 — e.g., cessation of conduct]

RESPONSE DEADLINE:
[Client] demands a response to this letter within [number] days of receipt, no
later than [specific date]. [Include any statutory notice period requirements if
applicable.]

CONSEQUENCES OF NON-RESPONSE:
If we do not receive a satisfactory response within the time specified above,
[client] is prepared to [file suit / pursue all available legal remedies /
file a complaint with (regulatory body) / etc.] without further notice. In that
event, [client] will seek all damages permitted by law, including [attorney's
fees, costs of litigation, statutory penalties, etc.] as applicable.

[Optional: Settlement/negotiation invitation — "We remain open to resolving this
matter amicably and invite you to contact our office to discuss a resolution."]

This letter is written without prejudice to any rights, claims, or remedies of
[client], all of which are expressly reserved.

Sincerely,

[Attorney Name — to be signed]
[Bar Number]
[Firm Name]
[Phone / Email]

Enclosures: [List any attached documentation]

cc: [Client name]
    [Other parties as appropriate]

Read the full file on GitHub · 141 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. 12d ago First seen · 141 lines · 13 tokens per session scan A d072adffe8fc

Subscribe to this mod's changes

demand-letter is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (26 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 1,275 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.