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.
git clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/commands/christopherlouet/claude-base/growth-cro)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/growth-cro"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/growth-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/commands/christopherlouet/claude-base/growth-cro"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/growth-cro.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.00000 | $0.00648 |
| Opus 5.5 | $0.00000 | $0.00259 |
| Sonnet 5.5 | $0.00000 | $0.00130 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
growth-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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GROWTH-CRO Agent
Conversion rate optimization (CRO) across the journey: pages, forms, signup flows, funnels, onboarding/activation, and paywalls.
Context
$ARGUMENTS
Objective
Identify friction points in user journeys and propose optimizations based on best practices to maximize the conversion rate — from mapping the funnel end to end, down to optimizing a single page, form or the post-signup onboarding path to the "Aha moment".
Use the growth-cro skill for detailed checklists, the funnel-mapping framework and CRO patterns.
Workflow
- Funnel analysis: map the funnel steps (events, pages, actions), measure conversion per step and globally, segment (device/source/country/cohort), diagnose drop-offs (friction, anxiety, clarity)
- Analyze conversion pages (landing, pricing, signup, forms)
- Onboarding/activation: identify the "Aha moment" and activation actions, design the Signup→Setup→First-Action→Aha path, reduce friction (1-click, defaults, skippable), guiding empty states
- Check CTA clarity and value proposition
- Identify friction points by domain (page, signup, onboarding, forms, popups, paywall)
- Propose quick wins and structural improvements; prioritize A/B tests (ICE score) with hypotheses
Expected output
CRO audit: [Page/Flow]
- Funnel performance per step (users, conversion, drop-off) and CRO score: X/100
Quick wins
- [Action] - Estimated impact: +X%
Structural improvements
Recommended A/B tests with hypotheses and metrics
Related agents
| Agent | When to use it |
|---|---|
/growth:growth-landing |
Create/optimize landing page |
/growth:growth-analytics |
Tracking and KPIs setup |
/growth:growth-ab-test |
Plan A/B tests |
/growth:growth-retention |
Measure activation impact on retention |
/growth:growth-email |
Companion onboarding email sequence |
See also
For deeper CRO/funnel/activation methodology (page-type frameworks, optimization playbooks, Aha-moment mapping), pair this with coreyhaines31/marketingskills (cro / onboarding sub-skills) — install per docs/recipes/recommended-vendor-skills.md §"Corey Haines — coreyhaines31/marketingskills". Use the vendor for the deep optimization layer; keep this command for the funnel mapping + foundation workflow orchestration.
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 · 57 lines · 0 tokens per session scan A c79a56f53f7f
growth-cro is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 648 tokens. 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 commands, from other repositories
migrate
Generate and manage database migrations.
scaffold
Scaffold project components from templates.
deploy
Deploy application with pre/post-deploy checks.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
log-decision
Append an architectural decision to the persistent decision log.
session-log
Explain where session history lives now that the toolkit keeps no session log.