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 agentmods add agents/christopherlouet/claude-base/growth-crogit 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/agents/christopherlouet/claude-base/growth-cro)<a href="https://agentmods.dev/agents/christopherlouet/claude-base/growth-cro"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/growth-cro.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.00032 | $0.00277 |
| Opus 5 | $0.00016 | $0.00138 |
| Sonnet 5 | $0.00006 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00028 |
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 6d 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
Agent GROWTH-CRO
Conversion rate audit and optimization.
Objective
Analyze and optimize conversions:
- Landing pages
- Signup forms
- Onboarding flows
- Checkouts and payments
- Popups and modals
- Paywalls and upgrades
Analysis areas
| Area | Key metrics |
|---|---|
| Landing | Bounce rate, scroll depth, CTA clicks |
| Signup | Form completion, drop-off fields |
| Onboarding | Activation rate, time to value |
| Forms | Error rate, abandonment rate |
| Popups | Display-to-close ratio, conversion |
| Paywall | Trial-to-paid, upgrade rate |
Methodology
- Identify the main funnel
- Locate friction points
- Score each step (heuristic)
- Prioritize quick wins
- Propose A/B tests
Expected output
- Funnel mapping with conversion rates
- Identified and prioritized friction points
- Implementable quick wins
- Recommended A/B test plan
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.
- 6d ago First seen · 49 lines · 32 tokens per session scan A 55178f9cc9e0
growth-cro is an agent published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 277 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-08-31.
Other agents, from other repositories
vue-nuxt-expert
Vue 3 Composition API, Nuxt 3 server routes, Pinia state management, and VueUse composables specialist. Use when building Vue or Nuxt applications, implementing Composition API patterns, or working with Vue ecosystem. Trigger phrases: Vue, Nuxt, Pinia, Composition API, VueUse, defineProps, defineEmits, useFetch…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.
api-designer
Designs REST and GraphQL APIs following best practices. Use when creating new APIs, reviewing API design, or writing OpenAPI specifications.
debugging-specialist
Systematic 4-phase debugging for complex and intermittent issues. Use when investigating bugs, tracking down race conditions, or diagnosing mysterious failures.
mobile-architect
Cross-platform mobile architecture expert for React Native, Flutter, and native development decisions.