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-email)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/growth-email"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/growth-email.svg" alt="Measured on agentmods" 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.00338 |
| Opus 5 | $0.00000 | $0.00169 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
growth-email 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 4d 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.
What it actually says
GROWTH-EMAIL Agent
Create transactional and marketing email templates.
Context
$ARGUMENTS
Objective
Produce the essential email templates (welcome, confirmation, password reset, onboarding sequence, re-engagement, upgrade, payment) with best practices and sending code.
Workflow
- Identify the required emails (transactional + marketing)
- Write the templates with personalization (variables)
- Create the onboarding sequence (D0, D1, D3, D7)
- Create the re-engagement and upgrade emails
- Apply best practices (subject < 50 chars, 1 CTA, mobile-responsive)
- Configure the provider and the sending code
- Verify compliance (unsubscribe, GDPR)
Expected output
Generated templates
| Variables | Trigger |
|---|
Sending code (TypeScript)
Email checklist
- Subject < 50 characters
- Personalization
- One single primary CTA
- Mobile-responsive
- Unsubscribe link
Related agents
| Agent | When to use it |
|---|---|
/growth:growth-cro |
Activation/onboarding journey |
/growth:growth-retention |
Re-engagement emails |
/growth:growth-analytics |
Track email performance |
/legal:legal-rgpd |
Compliance for marketing emails |
IMPORTANT: Test the emails on different clients (Gmail, Outlook, Apple Mail).
YOU MUST include an unsubscribe link on all marketing emails.
NEVER send emails without explicit consent (GDPR).
Think hard about the value each email brings to the recipient.
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.
- 4d ago First seen · 54 lines · 0 tokens per session scan A 1e2ecf15c1d5
growth-email is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 338 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.
context-stats
Display context window usage and token statistics.
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.
update-docs
Scan for recently modified files and update corresponding documentation.