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 w95/awesome-claude-corporate-skills --skill onboarding-playbookgit clone --depth 1 https://github.com/w95/awesome-claude-corporate-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/w95/awesome-claude-corporate-skills/onboarding-playbook)<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/onboarding-playbook"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/onboarding-playbook/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/w95/awesome-claude-corporate-skills/onboarding-playbook"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/onboarding-playbook.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.00023 | $0.04050 |
| Opus 5 | $0.00012 | $0.02025 |
| Sonnet 5 | $0.00005 | $0.00810 |
| Haiku 4.5 | $0.00002 | $0.00405 |
Grade A, and why
onboarding-playbook 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 — 593 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboarding Playbook
Overview
Design comprehensive onboarding playbooks that accelerate time-to-value, ensure customer success, and build strong product adoption. Effective onboarding sets the foundation for long-term customer health, expansion, and retention.
Onboarding Goals
Primary Objectives:
- Get customer live on the product (time-to-value: <30 days)
- Achieve 80% adoption of core features within 60 days
- Build internal champion for product expansion
- Establish positive relationship and trust
- Enable customer to operate independently
Success Metrics:
- Time to first value: 7-14 days
- First 30 days: Core workflows operational
- By day 60: 80% core features adopted; team trained
- By day 90: Expansion conversation; roadmap discussion
- By month 6: Renewal conversation with confidence
Onboarding Playbook Template
Phase 1: Pre-Implementation (Days -7 to 0)
Week Before Go-Live:
Kickoff Meeting (30-60 min):
- Attendees: Customer PM/owner, IT lead, CSM, Implementation lead
- Agenda:
- Customer success plan overview
- Timeline and milestones
- Roles and responsibilities
- Success criteria definition
- Risk identification
Deliverables:
- Success plan documented (shared document)
- Timeline and key dates confirmed
- Customer DRI (Directly Responsible Individual) named
- Escalation path defined
- Communication cadence set (weekly check-ins)
Pre-Implementation Prep:
- Customer provides data (systems to integrate, data formats)
- Vendor prepares: Sandbox environment, test data, configurations
- Customer: Network access, credentials, IT approvals
- Vendor: Training materials, documentation, runbooks
Stakeholder Alignment:
Role | Name | Company | Responsibility | Communication Freq
-----|------|---------|-----------------|------------------
Executive Sponsor | [Name] | Customer | Executive alignment; approval | Monthly
Project Lead | [Name] | Customer | Day-to-day project ownership | Weekly
IT Lead | [Name] | Customer | System access; security; infrastructure | Weekly
Power Users | [Names] | Customer | Feature validation; training peers | 2x/week
CSM | [Name] | Vendor | Overall account; success planning | 2x/week
Implementation Lead | [Name] | Vendor | Technical implementation | 2x/week
Product SME | [Name] | Vendor | Feature training; workflow design | As needed
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 · 593 lines · 23 tokens per session scan A 1547c2a986e4
onboarding-playbook is a skill published in the GitHub repository w95/awesome-claude-corporate-skills (198 stars, last pushed 6mo ago), licensed MIT. It adds 23 tokens to every session and 4,050 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
workflow
Starts and manages autonomous agent workflows. Triggers: workflow, start workflow, autonomous agents, agent pipeline.
autonomous-dev
Drives a brief, specification, issue or existing PR through implementation, review, tests and QA to a ready PR. Persists ownership, progress and commit-bound evidence for safe resumption. Use for autonomous software delivery or finishing an interrupted development run.
onboard
Sets up ai-toolkit in a project: symlinks, CLAUDE.md, intent interview. Triggers: onboard, setup project, install ai-toolkit, migrate project.
plan
Breaks features/goals into phased plans with task lists, agent assignments, dependencies. Triggers: plan feature, implementation roadmap, break down task, project phases.
prd-to-issues
Splits a PRD into vertical-slice GitHub issues with HITL/AFK tagging and dependencies. Triggers: PRD to issues, create tickets, break down PRD, work items.
prd-to-plan
Converts PRD into phased plan via tracer-bullet vertical slices. Triggers: PRD to plan, break down PRD, implementation plan, tracer bullets, phased plan.