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 onboarding-handoffgit 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/onboarding-handoff)<a href="https://agentmods.dev/skills/etrebels/claude-code-growth-os/onboarding-handoff"><img src="https://agentmods.dev/badge/skills/etrebels/claude-code-growth-os/onboarding-handoff/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/onboarding-handoff"><img src="https://agentmods.dev/badge/skills/etrebels/claude-code-growth-os/onboarding-handoff.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.00061 | $0.00560 |
| Opus 5 | $0.00030 | $0.00280 |
| Sonnet 5 | $0.00012 | $0.00112 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
onboarding-handoff 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 — 24 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboarding Handoff (Won → onboarding)
The handoff most teams never define: a signed deal drops silently into a customer-success void, the value the buyer was sold gets lost, and the renewal clock starts late. This is handoff H3 in docs/operating-model.md — made concrete as a 48-hour checklist that turns a won deal into the first row of the account book.
From the won deal (point me at the row in ops/pipeline.md, or paste the deal context):
- Carry the value hypothesis forward. Write down, in one line, what the customer bought this to do — in their words, from discovery. This becomes the value hypothesis in
ops/customers.md, and the thing every adoption check is measured against. Lose it here and onboarding optimizes for activity, not value. - Set the date markers. Record the renewal date, the contract value (ARR — the number the book rolls up to NRR), and note the day-60 renewal-motion trigger (not day-85). Set a first-expansion check date too — the moment to look for a second team or use case.
- Identify the power user / champion. Name who will actually use it and who sponsors it internally. A single-threaded account is a churn risk before it's even live — if there's only one name, that's the first gap to close.
- Write the first adoption milestone. One concrete, dated outcome that proves value is landing (the first workflow live, the first cross-system answer, the first report shipped). Vague onboarding has no finish line.
- Open the row. Create the account in
ops/customers.mdat stage Onboarding, with the value hypothesis, the ARR, the first adoption signal to watch, the renewal date, an owner, and the next step. Offer to log the handoff inops/daily-log.md.
Don't invent commitments the deal didn't contain. Bring your own onboarding playbook; this carries the deal's context across the seam so nothing drops.
Depth
- quick: open the
ops/customers.mdrow with value hypothesis, renewal date, and owner. - standard: the full 48-hour checklist above.
- deep: + a single-threading risk read and the first two adoption milestones with dates.
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 · 24 lines · 61 tokens per session scan A 6e26c741e7b9
onboarding-handoff is a skill published in the GitHub repository etrebels/claude-code-growth-os (20 stars, last pushed 3d ago), licensed MIT. It adds 61 tokens to every session and 560 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
support-tool-stack
Customer support platform selection, setup, and optimization — Intercom, Zendesk, Front, Help Scout, HubSpot Service Hub, Linear, and AI-native tools. Use when choosing a support platform, migrating tools, setting up help desk workflows, designing ticket routing, building macros and saved replies, or integrating…
co-founder-dynamics
Complete co-founder playbook for technical founders — finding co-founders, equity splits (dynamic and static), co-founder agreements, vesting schedules, working relationships, conflict resolution, co-founder breakups, and the "dating before marrying" framework. Use when looking for a co-founder, structuring a founding…
engineer-to-founder
Translate engineering strengths into founder-led GTM: customer discovery, positioning, demos, technical proof, founder sales habits, and first repeatable motion. Use when a technical founder needs to sell, do customer interviews, explain value without feature dumping, or build GTM confidence.
sla-management
Design and manage customer support SLAs — service level agreements, ticket priority matrices, first response time targets, resolution time targets, escalation paths, business hours configuration, and SLA performance dashboards. Use when defining support SLAs, building tier-based service levels, designing escalation…
advisor-recruitment
Strategic advisor recruitment for B2B SaaS founders. Use when building advisory board, recruiting individual advisors, structuring advisor compensation (equity grants), defining advisory scope, leveraging advisors for intros/references/customers, and managing ongoing advisor relationships.
first-hires-playbook
Complete playbook for founder's first 10 hires beyond sales. Use when hiring first engineer, first CS, first marketer, first product manager, or building founding team. Covers when to hire each role, job description architecture, compensation benchmarking, interview process design, and offer construction.