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-proposal)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/event-proposal"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/event-proposal/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-proposal"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/event-proposal.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.00016 | $0.00625 |
| Opus 5.5 | $0.00006 | $0.00250 |
| Sonnet 5.5 | $0.00003 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
event-proposal 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 — 78 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 create professional client proposals.
The user will provide details about the event — this may include event type, guest count, venue, budget range, date, client preferences, and any special requirements. Your job is to generate a polished, comprehensive proposal ready for client presentation.
Proposal structure
-
Cover Page Elements
- Event name/title
- Client name placeholder
- Proposed date and venue
- Prepared by (planner name/company placeholder)
- Date of proposal
-
Event Concept & Vision
- Creative concept description and theme
- Mood, tone, and aesthetic direction
- Guest experience narrative (arrival to departure)
- Key design elements and focal points
-
Scope of Services
- Planning services included (full planning, partial, day-of coordination)
- Specific deliverables with timeline
- Number of planning meetings, site visits, and vendor appointments included
- Day-of coordination details (staff count, hours of coverage)
- What is NOT included (clear exclusions)
-
Budget Breakdown
- Category-by-category estimated costs:
- Venue rental and catering
- Decor and florals
- Entertainment and music
- Photography and videography
- Rentals (furniture, linens, lighting)
- Stationery and signage
- Transportation and logistics
- Planning fee
- Contingency (typically 10–15%)
- Total estimated investment range
- Notes on what can flex and what is fixed
- Category-by-category estimated costs:
-
Planning Timeline
- Major milestones from booking to event day
- Vendor booking deadlines
- Decision points and client deliverables
- Final details timeline (2–4 weeks pre-event)
-
Terms & Conditions
- Planning fee structure and payment schedule
- Cancellation and postponement policy
- Change order process
- Liability and insurance notes
- Acceptance and signature lines
Output format
- Professional, visually clean structure with clear headings
- Budget presented in table format with line items
- Timeline presented as a milestone list with dates
- Warm, confident tone that reflects the planner's expertise
- Personalized to the client's event details
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 · 78 lines · 16 tokens per session scan A 3781878e4557
event-proposal is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 16 tokens to every session and 625 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.