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 etrebels/claude-code-growth-os --skill event-to-pipelinegit clone --depth 1 https://github.com/etrebels/claude-code-growth-osWrote 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/etrebels/claude-code-growth-os/event-to-pipeline)<a href="https://agentmods.dev/skills/etrebels/claude-code-growth-os/event-to-pipeline"><img src="https://agentmods.dev/badge/skills/etrebels/claude-code-growth-os/event-to-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/etrebels/claude-code-growth-os/event-to-pipeline"><img src="https://agentmods.dev/badge/skills/etrebels/claude-code-growth-os/event-to-pipeline.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.00051 | $0.00600 |
| Opus 5 | $0.00026 | $0.00300 |
| Sonnet 5 | $0.00010 | $0.00120 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
event-to-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 12d 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 — 26 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Event → Pipeline
An event is for booking calls, not holding them. In a room of 30–50 people you can't run real conversations on the floor — the win is a short, specific touch that ends in a call booked two or three days out.
- Lead with a call-earning offer, not a pitch. Offer one small, genuinely useful thing that makes a 15-minute call worth their time — an outline of where you'd start, a teardown of one thing, a second opinion. Frame it as your read, hedged ("where I'd start"), never their numbers. If you limit it, make the limit true — it costs real prep hours, so "I can only do a few of these properly" is honest; an invented "only 5 spots" is not.
- Book the next step on the spot. Keep a QR code to your booking link on your phone. "Worth 15 minutes Thursday?" + scan now beats "I'll follow up." Know your week well enough to offer two concrete slots.
- Discern fit fast. Sort each person as you go: a fit worth a call, a wrong-fit to be warm to and move on from, or someone whose need is a different offer than the one you lead with. Don't spend a room's worth of time on the biggest logo if they can't buy what you do.
- Don't over-send afterward. A document emailed before the call gives a busy person a reason to say no alone. Get them on the call first; material follows.
- Follow up within 48–72h, while they still remember meeting you. A warm, in-person lead outranks anything on your cold list — work these first.
When they hesitate (Chris Voss, Never Split the Difference)
"Let me think about it" → a calibrated question, then silence: "That's fair — what specifically would you want to think through?" Calibrated questions start with What or How, never "why". Don't let them set the agenda by deferring to email — name the next step and put it in the calendar.
Bring your own proof and your own voice; don't fabricate offers, names, or numbers.
Depth
- quick: the call-earning offer + the one-line ask to book.
- standard: the full play above, tuned to this event (who's likely there, the offer, two slots).
- deep: + a per-segment sort (prioritise vs be-warm-and-move-on) and a 48–72h follow-up note ready to send.
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.
- 12d ago First seen · 26 lines · 51 tokens per session scan A 995b690e9434
event-to-pipeline is a skill published in the GitHub repository etrebels/claude-code-growth-os (20 stars, last pushed 6d ago), licensed MIT. It adds 51 tokens to every session and 600 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
startup-launch-playbook
A step-by-step playbook for early-stage startups going from pre-seed to their first 1000 users. Covers MVP validation, initial traction channels, and founder-led growth tactics. By @WeiYipei — follow on X for more startup growth insights.
campaign-analytics
Analyze campaign performance from deliverability through revenue: delivery, engagement, replies, meetings, SQOs, pipeline, CAC, and payback. Produces diagnostic scorecard, root-cause analysis, benchmark comparison, and next-action plan. Use when deciding whether to scale, fix, or kill campaigns.
gtm-metrics
Build a GTM metrics system for SaaS: funnel conversion, pipeline velocity, win rates, CAC, payback, NRR, sales efficiency, growth accounting, and executive dashboards. Use when creating metrics dashboards, board reports, revenue reviews, operating cadence, or diagnosing growth constraints.
a-b-testing
Design statistically sound GTM experiments for copy, channels, landing pages, sequencing, pricing, and funnel conversion. Produces hypothesis, sample-size logic, success metrics, test plan, analysis method, and scale/stop/kill recommendation. Use when planning A/B tests, split tests, or experiment roadmaps.
attribution
Build practical B2B attribution models across first touch, lead creation, opportunity creation, multi-touch, account-based influence, and sales-sourced revenue. Produces model comparison, UTM governance, source-of-truth rules, and channel ROI view. Use when marketing and sales disagree on source or ROI.
deliverability-monitoring
Monitor outbound deliverability health across domains, inboxes, DNS, bounces, spam placement, reply rates, and reputation signals. Produces alert thresholds, dashboard spec, weekly QA checklist, and remediation playbook. Use when inboxing drops, bounce rates rise, campaigns underperform, or new infrastructure launches.