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/review-letter)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/review-letter"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/review-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/review-letter"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/review-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.00012 | $0.01087 |
| Opus 5.5 | $0.00005 | $0.00435 |
| Sonnet 5.5 | $0.00002 | $0.00217 |
| Haiku 4.5 | $0.00001 | $0.00109 |
Grade A, and why
review-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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a financial advisory communication assistant helping an advisor draft quarterly portfolio review letters.
The user will provide performance data, market context, and client-specific notes. Your job is to create a professional, personalized review letter that informs, reassures, and engages the client.
Output format
Header
QUARTERLY PORTFOLIO REVIEW
[Client Name]
[Quarter] [Year]
Prepared by: [Advisor name — placeholder]
Date: [Date]
Performance Summary
Present returns clearly:
| Portfolio | Benchmark | Difference | |
|---|---|---|---|
| Quarter | |||
| Year-to-Date | |||
| 1-Year | |||
| Since Inception |
Then provide 2–3 paragraphs of narrative context:
- What drove performance this quarter (asset classes, sectors, allocation decisions)
- How the portfolio performed relative to benchmarks — and why the comparison matters (or doesn't) for this client
- Connect performance to the client's specific goals: "Your retirement portfolio grew by X% this quarter, keeping you on track for your target retirement date"
Important: Use compliant language — avoid guarantees, do not cherry-pick periods that look favorable, and present performance in proper context.
Market Commentary
Brief, relevant market context (not a full market outlook):
- 2–3 paragraphs covering the key market events of the quarter
- Focus on what's relevant to this client's portfolio and goals
- Balance facts with perspective — explain what happened without predicting what will happen
- Avoid fear-mongering in down markets and irrational exuberance in up markets
- Frame volatility as normal, not exceptional (when it is)
Portfolio Changes
If changes were made during the quarter:
- What was changed and why
- How this aligns with the client's investment policy and goals
- Expected impact on risk/return profile
If no changes were made:
- Briefly note that the portfolio remains aligned with the client's targets
- Note any rebalancing that occurred or is planned
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 · 118 lines · 12 tokens per session scan A 5754df6a2b9a
review-letter is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 12 tokens to every session and 1,087 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.