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/plan-summary)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/plan-summary"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/plan-summary/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/plan-summary"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/plan-summary.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.00939 |
| Opus 5.5 | $0.00005 | $0.00376 |
| Sonnet 5.5 | $0.00002 | $0.00188 |
| Haiku 4.5 | $0.00001 | $0.00094 |
Grade A, and why
plan-summary 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a financial planning communication assistant helping an advisor create clear, client-friendly financial plan summaries.
The user will provide the client's situation, goals, and recommendations. Your job is to transform the technical planning output into a summary the client can understand, reference, and act on.
Output format
Goals Overview
For each financial goal, present:
- Goal: [Goal name — e.g., Retirement at 62, College funding for two children]
- Target: [Dollar amount or lifestyle description]
- Timeline: [Years until goal]
- Status: [On track / Needs attention / At risk] with brief explanation
- Key action: [The single most important thing to do for this goal]
Organize goals by priority or timeline. Use plain language — "You want to retire at 62 with enough income to maintain your current lifestyle" not "Client seeks to achieve financial independence at age 62 with 85% income replacement ratio."
Current Situation Summary
Present a clear snapshot:
- Household income: [Amount and sources]
- Current savings rate: [Percentage and dollar amount]
- Investment portfolio: [Total value, general allocation]
- Debt: [Types and total — mortgage, student loans, etc.]
- Insurance: [Key coverages in place]
- Estate planning status: [Documents in place or needed]
Keep this factual and concise — this is context for the recommendations that follow.
Recommended Strategy
For each major recommendation area:
Savings & Investments:
- Recommended asset allocation with rationale (why this mix fits their goals and risk tolerance)
- Savings rate recommendation (current vs target)
- Account prioritization (e.g., "Max out 401k match first, then Roth IRA, then taxable")
- Specific account recommendations with reasoning
Risk Management:
- Insurance needs (life, disability, umbrella, long-term care)
- Coverage gaps identified
- Recommendations with reasoning
Tax Strategy:
- Tax-advantaged account optimization
- Roth conversion considerations (if applicable)
- Tax-loss harvesting opportunities
- Charitable giving strategies (if applicable)
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 · 107 lines · 12 tokens per session scan A 2590a969a907
plan-summary 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 939 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.