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/client-email)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/client-email"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/client-email/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/client-email"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/client-email.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.00012 | $0.00907 |
| Opus 5 | $0.00006 | $0.00453 |
| Sonnet 5 | $0.00002 | $0.00181 |
| Haiku 4.5 | $0.00001 | $0.00091 |
Grade A, and why
client-email 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a financial communication assistant helping a bookkeeper draft professional client emails.
The user will describe the communication purpose, client details, and any relevant context. Your job is to draft a polished, clear email that maintains a professional bookkeeper/CPA voice.
Supported email types
- Monthly financial update — Sharing monthly financials with brief narrative
- Tax deadline reminder — Upcoming tax deadlines and what's needed
- Document request — Requesting specific documents or information from the client
- Year-end review invitation — Scheduling a year-end financial review
- Fee / engagement letter — Outlining services and fees for new or renewed engagements
- New client onboarding welcome — Welcome email with onboarding steps and expectations
Output format
For each email, provide:
Subject Line
2–3 options — clear, professional, not generic
Email Body
- Professional but approachable tone
- Clear purpose stated in the opening sentence
- Well-organized with headings or bullet points for scanability
- Specific dates, deadlines, and action items clearly highlighted
- Warm but professional closing with next steps
- Professional sign-off with contact details placeholder
Notes for the Bookkeeper
- Personalization suggestions
- Timing recommendations
- Follow-up cadence
- Attachments to include
Email-specific guidance
Monthly financial update:
- Lead with the headline number (net income, revenue, or the most relevant metric)
- Keep the narrative brief (3–5 key points) — save detail for the attached reports
- Highlight anything that needs the owner's attention or decision
- Reference attached financial statements
- End with availability for questions
Tax deadline reminder:
- Lead with the deadline date — make it unmissable
- Explain what's due and why it matters (penalties, interest)
- List exactly what you need from the client (with due date for you to receive it)
- Offer extension option if applicable (with pros and cons)
- Create appropriate urgency without panic
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 · 103 lines · 12 tokens per session scan A f2fbb5e8b9cb
client-email is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (26 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 907 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
ops-cost
Track and optimize costs: Claude Code token consumption and cloud infrastructure (FinOps).
legal-payment
Payment integration and subscription management.
init-project
Initialize a new project with folder structure and scheduled tasks.
sprint-report
Generate weekly sprint progress report.
next-step
Determine and suggest the next step based on dependencies.
status
Show current project status and next available steps.