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 matteotitta/genesys-skills --skill event-pipelinegit clone --depth 1 https://github.com/matteotitta/genesys-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/matteotitta/genesys-skills/event-pipeline)<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/event-pipeline"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/event-pipeline/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/matteotitta/genesys-skills/event-pipeline"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/event-pipeline.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.00027 | $0.02468 |
| Opus 5 | $0.00014 | $0.01234 |
| Sonnet 5 | $0.00005 | $0.00494 |
| Haiku 4.5 | $0.00003 | $0.00247 |
Grade A, and why
event-pipeline 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 9d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Event Pipeline
An in-person event is a system with a hard capacity constraint. One person holds roughly 12–16 meetings in a five-hour day. Everything upstream — how long the target list is, how many artifacts get built, how many people you chase — is a function of that number. Skills that skip it produce 200-row target lists for days with fourteen slots.
This skill is the in-person sibling of webinar-brief. That one is virtual and owns the run-of-show; this one is physical and owns the pipeline.
Doctrine inherited
Output complies with output-tenets.md, output-simplicity.md and doc-output-structure.md.
Also binding: crawl-cost-discipline.md (free discovery before metered extraction), quantitative-evidence-floors.md (no ROI verdict below the floor), pii-redaction.md (delegate data), outbound-research-hygiene.md (dated signals only).
When to run
Invoke when:
- "we're sponsoring / exhibiting at / attending [event]"
- "plan our conference" / "trade show plan" / "what do we do at [event]"
- "event follow-up" / "we just got back from [event]"
- Any physical gathering with a delegate list: conference, trade show, summit, roundtable, awards dinner, self-hosted meetup
Do NOT invoke when:
- The event is virtual →
webinar-brief - There is no event anchor, just a named account list →
abm-campaign - The ask is only the follow-up email copy →
outreach-emails - The ask is only a booth handout →
one-pager
Inputs
| Input | Required? | Source |
|---|---|---|
| Event name, date, venue, format | required | User, plus the event site |
| Attendance mode (sponsor / exhibitor / attendee-only) | required | User — drives the whole day plan |
| Headcount attending, and who | required | User |
| ICP definition | required | icp-research |
| Messaging + value props | required | product-messaging |
| Account scores | recommended | lead-scoring, or the client CRM |
| Client CRM + sending stack | recommended | Client CLAUDE.md — never assume; see the premium reference |
| All-in event cost | recommended | User — needed for the economics model |
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.
- 9d ago First seen · 155 lines · 200 tokens per session scan A 9baf54f27dcb
event-pipeline is a skill published in the GitHub repository matteotitta/genesys-skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 2,468 once invoked, about $0.0001 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
gingiris-b2b-growth
🇺🇸 B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF. PLG/SLG selection by ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate & channel motion, enterprise tiering. Built from HeyGen, Deel, Vercel, Supabase, Snowflake patterns.…
gr-b2b-growth
A guide to growing a business-to-business software product from early user research to large-scale sales. B2B software is sold to companies rather than individual consumers.
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
gingiris-go-global
🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization. A full-cycle playbook covering Phase 0-5 (market validation, positioning, first 100 users, user interviews, beta-to-growth) plus open-source launch, Product Hunt, Reddit, SEO/GEO, conversion, and org principles.…
gr-competitor-research
Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI…
ai-launch-playbook
Launch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.