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.
npx skills add travisjneuman/.claude --skill event-plannergit clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/skills/travisjneuman/.claude/event-planner)<a href="https://agentmods.dev/skills/travisjneuman/.claude/event-planner"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/event-planner/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/skills/travisjneuman/.claude/event-planner"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/event-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.03445 |
| Opus 5 | $0.00018 | $0.01723 |
| Sonnet 5 | $0.00007 | $0.00689 |
| Haiku 4.5 | $0.00004 | $0.00345 |
Grade A, and why
event-planner 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 8d 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 — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Event Planner
Comprehensive frameworks for planning, executing, and evaluating events of all types and scales.
Event Planning Timeline
12+ Months Out
- Define event purpose, goals, and success metrics
- Establish preliminary budget
- Select event date (check for conflicts)
- Form planning committee / assign roles
- Begin venue research and site visits
- Identify target audience and estimated attendance
- Determine event format (in-person, hybrid, virtual)
9-12 Months Out
- Book venue and sign contract
- Secure keynote speakers / entertainment
- Select and book caterer
- Begin sponsorship outreach
- Register event domain / create landing page
- Establish event branding (logo, theme, colors)
- Research and book AV vendor
6-9 Months Out
- Finalize budget allocations
- Open registration / ticket sales
- Book hotel room blocks (if overnight event)
- Hire photographer / videographer
- Plan menu with caterer (dietary accommodations)
- Design and order promotional materials
- Begin social media marketing campaign
- Recruit and train volunteers
3-6 Months Out
- Send formal invitations / email campaigns
- Confirm all vendor contracts and deposits
- Finalize event agenda and session schedule
- Arrange transportation / shuttle services
- Order signage, banners, and name badges
- Set up registration management system
- Coordinate speaker logistics (travel, AV needs)
- Plan networking activities / icebreakers
1-3 Months Out
- Send reminder communications to registrants
- Finalize floor plan and seating arrangements
- Confirm final headcount with caterer
- Prepare printed materials (programs, handouts)
- Brief all staff and volunteers
- Create day-of run sheet (see template below)
- Test all technology (AV, streaming, Wi-Fi)
- Finalize emergency and contingency plans
Final Week and Day Before
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.
- 8d ago First seen · 353 lines · 37 tokens per session scan A be87e160a16e
event-planner is a skill published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 6d ago), licensed MIT. It adds 37 tokens to every session and 3,445 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
incremental-shipping
Use when implementing a non-trivial feature, migration, or refactor that would otherwise be a single large change. Activate for keywords like "feature flag", "incremental", "vertical slice", "migration", "rollout", "behind a flag", "ship small". Enforces vertical slicing, feature-flagged rollout, and refactor-with…
toolbox
Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing…
bootstrap-monorepo
Autonomous polyglot monorepo bootstrap meta-prompt on the moon + proto + Bun stack (Nx-convergent). TRIGGERS - new monorepo, new repository, polyglot setup, scaffold repo, moon proto bootstrap, monorepo from scratch.
plan-review-experience
Experience-dimension reviewer for written plans (UX + DX). Use when running plan-review or directly when an experience review is wanted. Activate for keywords like "UX review", "DX review", "experience review", "error states", "API ergonomics", "developer experience", "user states". Scores 5 sub-dimensions 0-10…
issue-triage
Use when the user wants to triage GitHub issues - decide whether an issue is still relevant, reproducible, closeable, a duplicate, or what concretely needs doing. Selects and prioritizes first (never dumps all issues at once), then deep-triages the chosen issues via parallel subagents, recommends actions for the owner…
requirements-verbatim
Capture a user requirement, decision, approval, or constraint word-for-word into an append-only dated log so it survives context compaction and can never be trimmed, softened, or reinterpreted. Use whenever the user states or approves a requirement, gives a GO, sets a constraint, or makes any decision that later work…