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 OneWave-AI/claude-skills --skill onboarding-checklistgit clone --depth 1 https://github.com/OneWave-AI/claude-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/onewave-ai/claude-skills/onboarding-checklist)<a href="https://agentmods.dev/skills/onewave-ai/claude-skills/onboarding-checklist"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/onboarding-checklist/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/onewave-ai/claude-skills/onboarding-checklist"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/onboarding-checklist.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.00042 | $0.00575 |
| Opus 5 | $0.00021 | $0.00287 |
| Sonnet 5 | $0.00008 | $0.00115 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
onboarding-checklist 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboarding Checklist Generator
Generate a comprehensive, customized client onboarding checklist saved as onboarding-checklist.md in the current working directory. The checklist is actionable, phase-structured, and tailored to the specific engagement type.
Contents
references/output-template.md-- Full output structure: header block, four phases, handoff criteria, formatting rules.references/engagement-types.md-- How to classify Consulting vs SaaS vs Agency, and per-type adaptation guidelines.references/task-banks.md-- Reference task pools per engagement type and phase.references/email-templates.md-- The five required email templates, their structure, and content guidelines.references/scaling-and-pitfalls.md-- Timeline and team-size scaling rules, common pitfalls, and the final quality checklist.
Required Inputs
Gather these before generating. If any are missing, ask for them explicitly:
- Client Type: Industry, company size, maturity (e.g., "Series B fintech startup").
- Services Purchased: Exact scope of work or product tiers.
- Team Size: Number of people on both provider and client sides.
- Tech Stack: Relevant technologies, platforms, tools, integrations.
- Timeline: Total onboarding duration and any hard deadlines.
Workflow
- Collect all five required inputs from the user.
- Classify the engagement type (Consulting, SaaS, or Agency) using
references/engagement-types.md. This classification drives the structure and tone of the entire checklist. - Select and customize tasks from
references/task-banks.md, adapting language, deadlines, and owners to the specific engagement. Reflect tech-stack items in relevant tasks. - Apply timeline scaling rules from
references/scaling-and-pitfalls.mdbased on the specified duration. - Apply team-size scaling rules from
references/scaling-and-pitfalls.mdbased on team composition. - Generate all five email templates with full body content per
references/email-templates.md. - Compile the complete
onboarding-checklist.mdfollowingreferences/output-template.md. Apply the per-type adaptations inreferences/engagement-types.md. - Verify the result against the quality checklist and common pitfalls in
references/scaling-and-pitfalls.md. - Write the file to the current working directory using the Write tool.
- Confirm completion and summarize key stats (total tasks, timeline, engagement type, file location).
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 42 lines · 42 tokens per session scan A 875cee6f6ee5
onboarding-checklist is a skill published in the GitHub repository OneWave-AI/claude-skills (291 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 575 once invoked, about $0.0002 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
after-action-report
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event.…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
mass-ulw
Drives dependency-ordered child work through the native workflow tool, one run per phase with retry/amend/send recovery. Use when the user asks for mass-ulw, a DAG of tasks, or fan-out work where some tasks must wait on others.
beta-program-management
Running closed and open betas that produce real signal. Beta participant selection, structured feedback collection, beta-to-GA decision criteria, and the difference between soft-launch (no structure, no signal), kitchen-sink (everyone in, no actionable feedback), and structured beta (calibrated cohort, intentional…
okr-design
OKR design as actually shipped, not as conference-talk theory. Outcome statements that drive decisions, key results that measure the right thing, scoring discipline, mid-quarter recalibration, and the difference between sandbagged OKRs (always 100%) and aspirational OKRs (always 30%) and stretch OKRs (genuine ambition…
roadmap-planning
Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next…