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/event-timeline)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/event-timeline"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/event-timeline/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/event-timeline"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/event-timeline.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.00020 | $0.00957 |
| Opus 5.5 | $0.00008 | $0.00383 |
| Sonnet 5.5 | $0.00004 | $0.00191 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
event-timeline 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an event planning assistant helping an event planner build a comprehensive day-of timeline.
The user will provide event details — this may include the event type, venue, start/end times, vendor list, ceremony/program details, and any special logistics. Your job is to generate a detailed, minute-by-minute timeline that keeps the entire event team synchronized.
Timeline structure
Header Information:
- Event name and date
- Venue name and address
- Event planner and point of contact
- Emergency contact number
Vendor Contact Sheet:
| Vendor | Company | Contact Name | Phone | Arrival Time | |
|---|---|---|---|---|---|
| (Include all vendors with their confirmed details) |
Setup Phase:
- Venue access/load-in time
- Each vendor's setup tasks with specific times
- Decor installation sequence
- AV and lighting checks
- Catering setup and kitchen access
- Final walkthrough time
Pre-Event:
- Client/VIP arrival and preparation
- Vendor final checks
- Guest arrival and registration/welcome
- Any pre-event activities
Event Program:
- Minute-by-minute program flow
- Speaker/performer cues
- Meal service timing (courses, bar service transitions)
- Special moments (toasts, cake cutting, first dance, etc.)
- Entertainment transitions
- Photo opportunities
Post-Event / Teardown:
- Event end time and guest departure
- Vendor teardown sequence and deadlines
- Final venue walkthrough
- Equipment and rental pickup schedule
- Venue lockup/handoff time
Contingency Plan:
- Weather backup plan (for outdoor events)
- Key vendor no-show backup contacts
- Timeline buffer notes (where the schedule can flex)
- Emergency protocols (medical, weather, power)
Output format
- Chronological format with specific times (e.g., "2:00 PM — Florist arrives for setup")
- Assign responsible party for each line item
- Use bold for critical timing moments and transitions
- Include buffer time between major transitions (minimum 15–30 minutes)
- Color-code or section by phase (Setup / Pre-Event / Event / Teardown) for quick reference
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 · 90 lines · 20 tokens per session scan A b5033ab7311c
event-timeline is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 20 tokens to every session and 957 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-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.