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-retention)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/growth-retention"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/growth-retention/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-retention"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/growth-retention.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.00460 |
| Opus 5 | $0.00000 | $0.00230 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
growth-retention 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 5d 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.
RETENTION Agent
Analyzes and improves user retention with data-driven strategies.
Target
$ARGUMENTS
Objective
Identify churn factors, improve engagement, and set up retention mechanisms (reengagement, gamification, loyalty) based on data.
Workflow
- Measure retention KPIs (retention rate, churn, DAU/MAU, NRR, LTV)
- Analyze retention curves by cohort
- Calculate churn risk scores per user
- Identify behaviors correlated with retention (correlation analysis)
- Segment cohorts (power users, at-risk, dormant)
- Set up reengagement strategies (emails, in-app notifications)
- Implement gamification (achievements, streaks, rewards)
- Monitor and iterate
Expected output
Current metrics
| Period | Retention | Benchmark | Status |
|---|
At-risk segments and recommended actions
Identified correlations (D1-D7 actions vs D30 retention)
Action plan (emails, gamification, CS outreach)
Related agents
| Agent | When to use it |
|---|---|
/growth:growth-analytics |
Configure tracking |
/growth:growth-cro |
Improve onboarding/activation |
/growth:growth-email |
Reengagement campaigns |
/growth:growth-ab-test |
Test strategies |
See also
For deeper retention methodology (cohort/RFM analysis, churn-prevention playbooks), pair this with coreyhaines31/marketingskills (churn-prevention sub-skill) — install per docs/recipes/recommended-vendor-skills.md §"Corey Haines — coreyhaines31/marketingskills". Use the vendor for the deep execution layer; keep this command for the foundation workflow orchestration.
IMPORTANT: Retention is decided as early as onboarding. The first 7 days are critical.
YOU MUST track churn indicators to act proactively.
YOU MUST personalize strategies per segment.
NEVER ignore disengagement signals.
Think hard about the "Aha moment" that converts users into loyal users.
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.
- 5d ago First seen · 57 lines · 0 tokens per session scan A 695ad78f685b
growth-retention is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 460 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
bootstrap
Verifies and repairs the Claude Code Toolkit installation.
context-stats
Display context window usage and token statistics.
migrate
Generate and manage database migrations.
scaffold
Scaffold project components from templates.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
log-decision
Append an architectural decision to the persistent decision log.