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 agentmods add skills/jayrha/agentskills/event-plannernpx skills add JayRHa/AgentSkills --skill event-plannergit clone --depth 1 https://github.com/JayRHa/AgentSkillsWhat 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 | $0.00108 | $0.01187 |
| Opus 5 | $0.00054 | $0.00593 |
| Sonnet 5 | $0.00022 | $0.00237 |
| Haiku 4.5 | $0.00011 | $0.00119 |
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 2d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Event Planner
Overview
This skill plans an event from concept to run-of-show: it sets the budget envelope, sizes the guest list and venue, builds a backward-planned timeline from the event date, assembles the vendor/task checklist, writes the day-of run-of-show, and bakes in contingencies (weather, no-shows, vendor failure).
Keywords: event planning, party, wedding, birthday, dinner party, offsite, conference, fundraiser, guest list, venue, catering, run of show, event timeline, vendor checklist, RSVP.
When to use vs. not
Use this to plan and coordinate the shape and logistics of an event. It doesn't book vendors or guarantee live prices/availability — tell the user to confirm quotes, capacity, and contracts directly. For large/high-risk events (permits, alcohol licensing, crowd safety), flag that professional/licensed help and local regulations apply.
Inputs to gather first
- Event type, purpose, and vibe (formal/casual, the feeling you want).
- Date(s), or flexibility, and guest count (and who).
- Total budget and what it must cover.
- Location/region (indoor/outdoor, home/venue) and any constraints.
- Must-haves (specific food, accessibility, kids, dietary needs) and known risks (weather, travel).
Workflow
- Lock the frame. Confirm type, date, headcount, budget, and vibe in a few lines. These four — date, headcount, budget, venue — constrain everything else and should be decided first.
- Set the budget envelope. Split the total across the big rocks (venue, food & drink, and for weddings/large events the catering+venue often eat 50%+). Reserve a 10–15% contingency. See
references/budget-and-vendors.md. - Size venue to guest list. Confirm capacity, layout, parking/transit, restrooms, A/V, and whether catering is in-house or external. Build a backup venue/plan for outdoor events.
- Build the guest + invite plan. Headcount → invites with RSVP deadline → track responses → assume some no-show rate (and over-invite if a target headcount matters). Capture dietary/accessibility needs at RSVP.
- Backward-plan the timeline. Work back from the event date to today with milestones (book venue → send invites → finalize menu → confirm vendors → final headcount → day-of). See
references/timeline.md. - Assemble the vendor/task checklist. Catering, drinks, cake, décor, A/V, photography, music/entertainment, rentals, transport. For each: quote, deposit, confirmation date, point of contact.
- Write the run-of-show. A minute-by-minute day-of schedule: setup, guest arrival, key moments (toasts, cake, speeches), meals, teardown — with an owner per block.
- Plan contingencies. Weather backup, vendor no-show plan, extra food buffer, a day-of point person, and an emergency kit. Confirm everything 48–72 h before.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 61 lines · 108 tokens per session scan A 97e3c2329edb
event-planner is a skill published in the GitHub repository JayRHa/AgentSkills (4 stars, last pushed 1mo ago), licensed MIT. It adds 108 tokens to every session and 1,187 once invoked, about $0.0005 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-31.
Other skills, from other repositories
reverse-engineering-tools
Guide for reverse engineering protected games and anti-cheat components across user mode, kernel mode, and hypervisor-aware environments. Use this skill when analyzing drivers, IOCTL protocols, callback registration, injected-code artifacts, integrity checks, protected binaries, or debugging security-sensitive game…
unity-agent-workflows
Use for AI-assisted Unity work that needs live repo discovery, project-derived routing, runtime-owner proof, runtime-visible output hard stops, runtime numeric proof for repeated visible-output failures, state-step guards, multi-agent scope ownership, modular C#/asmdef safety, UI/scene/visual asset gates, data-first…
interpreting-mod-author-instructions
Use when deciding how to correctly download/install a Bethesda mod per the author's instructions — triggers "how do I install", "FOMOD choices", "which file to download", "author说明", "install instructions", "which variant", "按作者说明安装", "这个mod怎么装". NOT for deciding whether to include the mod (use evaluating-bgs-mods)…
using-bgs-archive
Use when the user wants to inspect, list, extract, unpack, or repack Bethesda BA2/BSA archives; determine archive format/version/compression; or build archive assets for an MO2 overlay. Triggers - "unpack BA2", "extract BSA", "pack archive", "inspect archive", "bgs-archive".
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.
design-director
Используй только внутри активного Codex Project Autopilot-проекта, когда уже выбрана проектная фаза и нужен design direction по плану автопилота.