Claude Code Templates is a command-line tool and catalogue for configuring Anthropic’s Claude Code with agents, commands, settings, hooks, integrations, skills, and project templates. Developers use it to browse and install reusable components for their coding workflows. The catalogue includes many of these Claude Code components.
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 davila7/claude-code-templates --skill onboarding-crogit clone --depth 1 https://github.com/davila7/claude-code-templatesWrote 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/davila7/claude-code-templates/onboarding-cro)<a href="https://agentmods.dev/skills/davila7/claude-code-templates/onboarding-cro"><img src="https://agentmods.dev/badge/skills/davila7/claude-code-templates/onboarding-cro/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/davila7/claude-code-templates/onboarding-cro"><img src="https://agentmods.dev/badge/skills/davila7/claude-code-templates/onboarding-cro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- 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.00093 | $0.02537 |
| Opus 5.5 | $0.00037 | $0.01015 |
| Sonnet 5.5 | $0.00019 | $0.00507 |
| Haiku 4.5 | $0.00009 | $0.00254 |
Grade A, and why
onboarding-cro 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 1mo 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.
Copies of this mod
5 near-identical copies found in the catalogue:
- onboarding-cro — 100% identical, 0 lines differ
- onboarding-cro — 100% identical, 0 lines differ
- onboarding-cro — 100% identical, 0 lines differ
- onboarding-cro — 95% identical, 3 lines differ
- onboarding-cro — 94% identical, 29 lines differ
How it starts
The opening of the file, as written. The whole thing — 434 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboarding CRO
You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention.
Initial Assessment
Before providing recommendations, understand:
-
Product Context
- What type of product? (SaaS tool, marketplace, app, etc.)
- B2B or B2C?
- What's the core value proposition?
-
Activation Definition
- What's the "aha moment" for your product?
- What action indicates a user "gets it"?
- What's your current activation rate?
-
Current State
- What happens immediately after signup?
- Is there an existing onboarding flow?
- Where do users currently drop off?
Core Principles
1. Time-to-Value Is Everything
- How quickly can someone experience the core value?
- Remove every step between signup and that moment
- Consider: Can they experience value BEFORE signup?
2. One Goal Per Session
- Don't try to teach everything at once
- Focus first session on one successful outcome
- Save advanced features for later
3. Do, Don't Show
- Interactive > Tutorial
- Doing the thing > Learning about the thing
- Show UI in context of real tasks
4. Progress Creates Motivation
- Show advancement
- Celebrate completions
- Make the path visible
Defining Activation
Find Your Aha Moment
The action that correlates most strongly with retention:
- What do retained users do that churned users don't?
- What's the earliest indicator of future engagement?
- What action demonstrates they "got it"?
Examples by product type:
- Project management: Create first project + add team member
- Analytics: Install tracking + see first report
- Design tool: Create first design + export/share
- Collaboration: Invite first teammate
- Marketplace: Complete first transaction
Activation Metrics
- % of signups who reach activation
- Time to activation
- Steps to activation
- Activation by cohort/source
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.
- 1mo ago First seen · 434 lines · 93 tokens per session scan A c973ee1520d8
onboarding-cro is a skill published in the GitHub repository davila7/claude-code-templates (32,942 stars, last pushed yesterday), licensed MIT. It adds 93 tokens to every session and 2,537 once invoked, about $0.0004 per session on Opus 5.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
hand-back
S7 of see-it-ship-it: what the person hears. Progress lines while building (percentage, fraction, three lines max), one-line celebration of real milestones credited to them, a session summary of done / fixed / next, and the fixed hand-back at the end: URL, table result, what to try by hand, what was learned versus…
ccc-adhd
Answer-first output: the fix, then command, then file:line, context last. Toggle on, off or status; stacks with caveman. Based on ayghri/i-have-adhd (MIT). Use when the user wants the answer first.
ccc-resume-session
Resume a saved session file: read it fully, then brief state, blockers and next step before any work. Use when continuing earlier work.
ccc-spawn
Spin self-contained work off on demand: a background subagent, a separate session (Cowork spawntask chip or CLI /spawn peer), or an independent expert pass; routes fan-outs to $ccc-fleet and chains to $ccc-relay. Use when the user types $ccc-spawn or wants a task done outside this thread.
ccc-yolo-setup
Cut approval prompts safely: keep auto permission mode, add a vetted read-only allowlist plus secret deny rules, back up settings, and set bypassPermissions only with explicit consent. Use when the user says yolo setup, reduce prompts, fewer approvals, or skip permissions.
team
Start long-lived provider LLM teammates as native Claude Code agent-team members (the native Agent tool with a ccf- type) that you message with SendMessage — multi-turn, collaborative, watchable in tmux panes. Use for sustained parallel build/work ("start 3 glm teammates", N teammates on N files), or when you need a…