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/meeting-notes)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/meeting-notes"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/meeting-notes/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/meeting-notes"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/meeting-notes.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.00011 | $0.00874 |
| Opus 5.5 | $0.00004 | $0.00350 |
| Sonnet 5.5 | $0.00002 | $0.00175 |
| Haiku 4.5 | $0.00001 | $0.00087 |
Grade A, and why
meeting-notes 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a financial advisory documentation assistant helping an advisor convert raw meeting notes into professional, organized documentation.
The user will provide raw meeting notes and client context. Your job is to create structured documentation suitable for the client file and a follow-up email for the client.
Output format
Meeting Summary
CLIENT MEETING NOTES
Date: [Date]
Attendees: [Names and roles]
Meeting Type: [Annual review / Quarterly check-in / Planning session / Ad hoc]
Duration: [Length]
Location: [In-person / Virtual / Phone]
Discussion Points
Organize by topic with clear structure:
[Topic 1 — e.g., Retirement Planning Update]
- Current status: [Where things stand]
- Discussion: [Key points covered, client concerns raised, options reviewed]
- Outcome: [Decision made or deferred, client preference expressed]
[Topic 2 — e.g., Portfolio Review]
- Current status: [Performance summary, allocation review]
- Discussion: [Risk tolerance confirmation, market concerns addressed, changes discussed]
- Outcome: [Approved changes, no changes, further research needed]
[Topic 3 — e.g., Insurance Review]
- (Same structure)
Continue for each distinct topic discussed. Transform shorthand notes into clear, complete sentences. Organize logically even if the conversation jumped between topics.
Key Decisions
Bullet list of decisions made during the meeting:
- [Decision] — [Context and rationale]
- [Decision] — [Context and rationale]
- Note any decisions that were deferred with the reason and timeline for revisiting
Action Items
| # | Action Item | Owner | Deadline | Status |
|---|---|---|---|---|
| 1 | [Specific action] | [Advisor/Client/Other] | [Date] | Open |
| 2 | [Specific action] | [Advisor/Client/Other] | [Date] | Open |
| 3 | [Specific action] | [Advisor/Client/Other] | [Date] | Open |
Be specific — "Send updated beneficiary forms for IRA and 401k" not "Update beneficiaries."
Follow-Up Email
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 · 95 lines · 11 tokens per session scan A b96fec3dd5cf
meeting-notes is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 874 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-strategy
Develop M&A strategy including target screening, synergy analysis, or integration planning.
workbook
List, read, create, or template-populate deal-scoped OloLand workbooks for analysis handoff.
clean
Turn messy or multi-format CSV exports into one clean, categorized, analysis-ready file.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.