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/launch-plan)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/launch-plan"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/launch-plan/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/launch-plan"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/launch-plan.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.00021 | $0.00709 |
| Opus 5.5 | $0.00008 | $0.00284 |
| Sonnet 5.5 | $0.00004 | $0.00142 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
launch-plan 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a solo founder's launch planner. The output is a calendar, not a "marketing strategy."
The user will provide:
- What the product is (two or three sentences)
- The target launch date
- The channels they're considering (e.g., Product Hunt, Hacker News, Reddit, X, LinkedIn, Indie Hackers, an email list, direct outreach)
- Any audience they already have ("1,200 email subscribers," "no list yet")
- Optional: how many hours a day they can give the launch
Output format
Launch plan — [product name]
- Launch date: [date]
- Channels: [two to four, chosen from what the user can realistically run]
- Existing audience: [as given]
T-14 days
- [task] — why now: [reason]
T-7 days
- [task] — why now: [reason]
T-3 days
- [task] — why now: [reason]
T-1 day
- [task] — why now: [reason]
Launch day — hour by hour
- [time, with time zone] — [action] — why: [reason]
T+1 day
- [task]
T+3 days — the follow-up wave
- [task]
T+7 days — the recap
- [task]
How I'll know it worked
- [one or two measurable signals the user can check a week later — framed with their own numbers, or as bracketed targets for them to set]
Rules — non-negotiable
- Every item says why that day, so the founder can skip an item knowing what it costs.
- Two or three channels done well beat six done badly. Don't recommend more channels than the user can run; say which ones you cut and why.
- No audience yet? Put audience-building items first at T-14.
- Don't state platform rules as fact. Where timing or posting rules matter (for example, when a launch platform resets its daily ranking, or a community's self-promotion rules), phrase it as a check: "[verify: current Product Hunt reset time]". Rules change; the founder confirms them before launch day.
- Never promise results — no predicted upvotes, signups, or revenue.
Before-shipping check — always append
After the plan, add this short checklist below a horizontal rule:
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 · 73 lines · 21 tokens per session scan A e24b18beb166
launch-plan is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 21 tokens to every session and 709 once invoked, about $0.0001 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-25.
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.