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 shawnpang/startup-founder-skills --skill event-hostinggit clone --depth 1 https://github.com/shawnpang/startup-founder-skillsWrote 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/shawnpang/startup-founder-skills/event-hosting)<a href="https://agentmods.dev/skills/shawnpang/startup-founder-skills/event-hosting"><img src="https://agentmods.dev/badge/skills/shawnpang/startup-founder-skills/event-hosting/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/shawnpang/startup-founder-skills/event-hosting"><img src="https://agentmods.dev/badge/skills/shawnpang/startup-founder-skills/event-hosting.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.00056 | $0.01650 |
| Opus 5 | $0.00028 | $0.00825 |
| Sonnet 5 | $0.00011 | $0.00330 |
| Haiku 4.5 | $0.00006 | $0.00165 |
Grade A, and why
event-hosting 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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- event-hosting — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Event Hosting
When to Use
- Founder wants to host a meetup, workshop, demo day, or community event
- Founder wants to use events to build pipeline, recruit, or establish thought leadership
- Founder wants to create a Luma event page with compelling copy
- Founder wants to plan a recurring event series to build community around their product or space
Context Required
- Event goal (lead generation, community building, recruiting, brand awareness, product feedback)
- Target audience (developers, founders, enterprise buyers, designers, etc.)
- Format (in-person, virtual, hybrid)
- Topic/theme and any confirmed speakers
- Capacity and venue (or virtual platform)
- Budget (many founder-hosted events are $0-500)
Workflow
- Define the event concept — clarify:
- Goal: what success looks like (X attendees, Y leads, Z brand impressions)
- Format: panel, workshop, demo night, fireside chat, networking, hackathon
- Audience: who should attend and why they'd show up
- Value prop for attendees: what they'll learn, who they'll meet, or what they'll get
- Write the event page — create copy for Luma (lu.ma) or similar platform:
- Title: specific and compelling (not "Tech Meetup #4" — instead "How 5 YC Founders Got Their First 100 Customers")
- Description: problem/hook → what you'll cover → who should attend → speaker bios → logistics
- Image/banner: recommend dimensions and style (Luma: 1600x900px)
- Plan the run of show — minute-by-minute agenda:
- Doors/login open (15 min buffer)
- Welcome and context (5 min — who you are, why this event exists)
- Main content (30-45 min — talks, panels, demos)
- Q&A or discussion (15 min)
- Networking / unstructured time (30 min for in-person)
- Close and next steps
- Build the promotion plan — how to fill seats:
- Post on relevant communities (use
community-discovery) - Personal outreach to 20-30 "anchor attendees" who make the event worth attending
- Cross-promotion with speakers' audiences
- LinkedIn/X posts from founder personal account
- Luma's built-in invite and reminder features
- Post on relevant communities (use
- Prepare follow-up — plan what happens after the event:
- Thank-you message to attendees (same day)
- Share recording/slides (if applicable)
- Connect with high-value attendees individually
- Announce next event (if recurring)
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.
- 11d ago First seen · 149 lines · 56 tokens per session scan A f23b5b921338
event-hosting is a skill published in the GitHub repository shawnpang/startup-founder-skills (321 stars, last pushed 5mo ago), licensed MIT. It adds 56 tokens to every session and 1,650 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…