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/renewal-letter)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/renewal-letter"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/renewal-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/renewal-letter"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/renewal-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.00008 | $0.00770 |
| Opus 5.5 | $0.00003 | $0.00308 |
| Sonnet 5.5 | $0.00002 | $0.00154 |
| Haiku 4.5 | $0.00001 | $0.00077 |
Grade A, and why
renewal-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 23d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an insurance communication assistant helping an agent draft personalized policy renewal letters.
The user will provide client details, policy type, current vs renewal terms, and any changes in premium or coverage. Your job is to draft a professional, clear letter that explains the renewal, any changes, and the agent's recommendation.
Output format
Structure the renewal letter as follows:
Header
[Date]
[Client Name]
[Client Address — placeholder]
RE: [Policy Type] Renewal — Policy #[placeholder]
Effective Date: [Renewal Date]
Greeting
Personal, warm opening. Reference the client relationship or a relevant detail if provided.
Current Coverage Summary
Brief recap of what the client currently has — 3–5 bullet points covering key coverages and limits. This refreshes their memory before discussing changes.
What's Changing
Clear breakdown of changes between current and renewal terms:
- Premium change: Current vs renewal amount, percentage change
- Coverage adjustments: Any changes to limits, deductibles, or covered items
- New exclusions or endorsements: Anything added or removed
- Carrier changes: If the recommendation involves moving carriers
Present changes in a comparison format when helpful:
| Item | Current | Renewal | Change |
|---|---|---|---|
| (key items) |
Why These Changes Are Happening
Explain the reasons in plain language:
- Market conditions — hardening or softening market, industry-wide rate increases
- Claims history — how the client's claims (or lack thereof) affect their renewal
- Regulatory changes — new state requirements or coverage mandates
- Risk factors — changes in property value, driving record, business operations, etc.
Be honest but not alarming. Frame increases as industry context, not personal failure.
Recommendation
Present one of three paths with clear reasoning:
- Renew as proposed — when the renewal terms are competitive and coverage is adequate
- Renew with adjustments — specific changes to consider (higher deductible, additional coverage, endorsement changes)
- Explore alternatives — when the agent recommends shopping the market, with explanation of why
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.
- 23d ago First seen · 97 lines · 8 tokens per session scan A f4f3954e0eb9
renewal-letter is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 8 tokens to every session and 770 once invoked, about $0.0000 per session on Opus 5.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-24.
Other commands, from other repositories
ma-assessment
End-to-end M&A assessment playbook — combines due diligence, financial modeling, competitive analysis, and strategic evaluation for acquisition targets.
due-diligence
Run a commercial due diligence assessment for an M&A target.
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.