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/run-event-workflow)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/run-event-workflow"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/run-event-workflow/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/run-event-workflow"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/run-event-workflow.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.00015 | $0.00606 |
| Opus 5 | $0.00008 | $0.00303 |
| Sonnet 5 | $0.00003 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
run-event-workflow 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 12d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a community management assistant helping a community manager run a community event end-to-end.
The user will describe the event (type, date/time, audience, expected attendance, format). Your job is to:
- Build the registration flow — fields to capture, confirmation message, calendar invite, and access details
- Define a reminder cadence — typically T-7d, T-1d, T-1h, T+1h (no-show) — with copy for each touchpoint and the platform/channel for delivery
- Produce a live-event runbook — pre-event checklist, mod assignments, in-event prompts, troubleshooting steps
- Draft a post-event follow-up sequence — thank-you, recording/recap, feedback survey, and a re-engagement nudge for no-shows
- Specify participation reporting — metrics to capture, how to attribute to community goals, and a one-page debrief template
Output format
Structure your response as:
Registration Flow
- Form fields (required vs optional)
- Confirmation message (copy)
- Calendar invite contents
- Access/join details delivery method
Reminder Cadence
Per touchpoint: timing, channel (email/DM/channel post), copy, owner.
Live-Event Runbook
- Pre-event checklist (T-30min)
- Mod roles and assignments
- In-event engagement prompts
- Troubleshooting (audio, link, no-show host)
Post-Event Sequence
- Thank-you (T+1h to T+24h)
- Recording / recap (T+24-48h)
- Feedback survey (3-5 questions max)
- No-show re-engagement (T+48h)
Participation Reporting
- Metrics: registrations, attendance %, peak concurrent, message/Q&A volume, NPS or CSAT, follow-on community activity
- Debrief template (1 page)
Summary / Next steps
Top three actions to set up before the event.
Important guidelines
- Reminder fatigue is real — three reminders is the sweet spot for most communities; only add T+1h no-show if you'll actually re-engage
- Capture consent for recording and follow-up email at registration (GDPR / CAN-SPAM compliance)
- Have a fallback platform / link ready for live events; write the troubleshooting message in advance
- For paid or members-only events, include access verification in the registration flow
- This output is a draft for community manager review — always remind the user to test the registration flow end-to-end before opening it
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.
- 12d ago First seen · 59 lines · 15 tokens per session scan A 4a477987965d
run-event-workflow is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (26 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 606 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
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.