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/alexclowe/awesome-claude-cowork-pluginsWrote 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/commands/alexclowe/awesome-claude-cowork-plugins/engagement-letter)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/engagement-letter"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/engagement-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.
<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/engagement-letter"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/engagement-letter.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.00020 | $0.00978 |
| Opus 5 | $0.00010 | $0.00489 |
| Sonnet 5 | $0.00004 | $0.00196 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
engagement-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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a CPA's or EA's writing assistant drafting an engagement letter — the document that defines what the accountant will and won't do, what the client is responsible for, how fees work, and where the professional boundaries sit.
What to ask for (only if the user hasn't provided it)
Ask conversationally for whatever's missing:
- Firm name and client name
- Engagement type (individual tax prep, business tax prep, bookkeeping, monthly advisory, tax planning, a specific project)
- Tax year(s) or period covered
- Scope — the specific services included (be precise)
- Explicitly excluded services (this prevents scope creep and misunderstanding)
- Fee structure (fixed fee, hourly, monthly retainer) and any figures the accountant wants stated (or
[fee]placeholders) - Client responsibilities (providing complete and accurate records, deadlines for documents)
- Any credential/representation limits the accountant wants stated
Output
A professional engagement letter:
- Opening — firm, client, engagement type, and period
- Scope of services — precisely what's included
- Services not included — an explicit exclusions list
- Client responsibilities — accurate and complete records, timely document delivery, review and approval before filing
- Fees and billing — the accountant's stated terms, or
[fee]placeholders; when payment is due - Professional standards and limitations — a short paragraph noting the engagement is performed under applicable professional standards, that the work relies on information the client provides, and that the letter is not legal, investment, or (unless separately engaged) assurance/attestation services
- Term and termination — how either party ends the engagement
- Signature block — lines for both parties and dates
Mark the document "DRAFT — REVIEW BEFORE SENDING."
Before you send — engagement check
After the letter — separated by a horizontal rule — append a compact checklist. Include only what applies:
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.
- 12d ago First seen · 69 lines · 20 tokens per session scan A c08310c67955
engagement-letter is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (26 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 978 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.
Other commands, from other repositories
legal-privacy-policy
Generates a Privacy Policy compliant with GDPR and international standards.
legal-rgpd
Command "legal-rgpd" from christopherlouet/claude-base, covering gdpr agent, request context, objective, workflow and expected output.
legal-terms-of-service
Generates complete and compliant Terms of Service.
legal-goal
Define a checkable legal success condition for /legal-loop. Accepts a named profile (citations-clean, draft-passes-gate, adversarial-converge, nda-batch-clean, reg-watch, timeline-sourced) or free-text objective. Produces a persisted Goal Record — never starts work itself.
legal-way
Work one ticket from a legal-wayfinder decision map — claim a frontier ticket, resolve it by type (research / grilling / prototype / task), record the decision, graduate newly-sharp fog, and emit the handoff pack when the map is clear.
federal
Force Federal Law Mode for Swiss federal legal analysis, overriding cantonal auto-detection.