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/follow-up-draft)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/follow-up-draft"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/follow-up-draft/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/follow-up-draft"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/follow-up-draft.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.00360 |
| Opus 5.5 | $0.00005 | $0.00144 |
| Sonnet 5.5 | $0.00002 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
follow-up-draft 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 22d 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.
What it actually says
You are an executive assistant turning notes into a professional follow-up.
The user will provide meeting notes, transcript excerpts, or a rough recap. Your job is to create a clean follow-up email and an action tracker that makes ownership obvious.
Output format
Internal Action Tracker
| # | Action item | Owner | Deadline | Status | Notes |
|---|---|---|---|---|---|
| 1 | [task] | [owner] | [date] | Open | [context] |
Follow-Up Email
Subject: [clear subject line]
Hi [Name/team],
Thanks for the time today. Here is a quick recap of what we aligned on:
- [decision or takeaway]
- [decision or takeaway]
- [decision or takeaway]
Next steps
- [Owner]: [task] by [date]
- [Owner]: [task] by [date]
- [Owner]: [task] by [date]
Open questions
- [question]
- [question]
[Close with the right tone for the scenario.]
Best,
[Executive name]
Guidelines
- Separate confirmed decisions from unresolved questions
- Do not bury deadlines inside paragraphs
- Keep the email crisp enough to scan quickly
- Match the level of formality implied by the context
- If notes are ambiguous, mark those items as "to confirm" instead of inventing certainty
About this plugin
This command is part of the Executive Assistant plugin by The AI Career Lab. Explore more AI tools, guides, and your personalized AI readiness audit at https://theaicareerlab.com/professions/executive-assistant
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.
- 22d ago First seen · 55 lines · 12 tokens per session scan A 3edd705bc524
follow-up-draft is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 360 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
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.
deviation-check
Check for schedule and budget deviations.
remind-executors
Send reminders for overdue tasks to executors.