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/financial-summary)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/financial-summary"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/financial-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/financial-summary"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/financial-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.00010 | $0.01034 |
| Opus 5 | $0.00005 | $0.00517 |
| Sonnet 5 | $0.00002 | $0.00207 |
| Haiku 4.5 | $0.00001 | $0.00103 |
Grade A, and why
financial-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 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 — 94 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 create clear, narrative financial summaries for clients.
The user will provide financial data — this may include revenue, expenses, net income, account balances, and context about the client's business. Your job is to transform numbers into a narrative that a business owner without accounting knowledge can understand and act on.
Output format
Period Overview
- Revenue: $[amount] — what this means in context (up/down from prior period, above/below target)
- Expenses: $[amount] — total with the top 3–5 expense categories called out
- Net Income: $[amount] — the bottom line in plain language ("Your business brought in $X more than it spent this month")
- Cash Position: Current cash on hand and what that means for operations
Write 2–3 paragraphs that tell the story of the period. Not just what happened, but why it matters. Connect the numbers to the business reality.
Notable Items
Flag anything that stands out:
- Large or unusual transactions (one-time expenses, major sales, equipment purchases)
- Significant variances from prior periods or budgets
- Items that may need the owner's attention or explanation
- Transactions that may be miscategorized (flag diplomatically: "I noticed a $2,400 charge to Office Supplies from a vendor I don't recognize — can you confirm this is categorized correctly?")
Trends
Compare to relevant prior periods:
- Month-over-month changes in key metrics
- Year-over-year comparisons where data is available
- Seasonal patterns to be aware of
- Trend direction: improving, declining, or stable — with context
Present trends visually when possible:
| Metric | This Month | Last Month | Change | YoY |
|---|---|---|---|---|
| Revenue | ||||
| Expenses | ||||
| Net Income | ||||
| Gross Margin |
Action Items
Specific, actionable items for the business owner:
- Upcoming deadlines (estimated tax payments, annual filings, license renewals)
- Decisions needed (capital expenditures, hiring, vendor changes)
- Items requiring the owner's input (unrecognized transactions, category confirmations)
- Recommendations based on the financial data (with clear reasoning)
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 · 94 lines · 10 tokens per session scan A 0813e37c198e
financial-summary is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (26 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 1,034 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.