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/agents/christopherlouet/claude-base/growth-analytics)<a href="https://agentmods.dev/agents/christopherlouet/claude-base/growth-analytics"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/growth-analytics/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/agents/christopherlouet/claude-base/growth-analytics"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/growth-analytics.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.00031 | $0.00469 |
| Opus 5.5 | $0.00012 | $0.00188 |
| Sonnet 5.5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
growth-analytics 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.
What it actually says
Agent GROWTH-ANALYTICS
Analytics and tracking implementation, plus post-launch data analysis on the collected events.
Workflow
- Choose the stack: GA4, Mixpanel, Posthog (self-hosted), or Segment
- Tracking plan: define events with the naming convention
[Object]_[Action] - Client implementation: trackEvent, trackPageView, identify, trackConversion
- Server-side: sensitive events (revenue) always server-side
- KPI dashboard: Acquisition (CAC), Activation, Engagement (DAU/MAU), Revenue (MRR/LTV), Retention
- Post-launch analysis: once events flow, run analytical SQL on the warehouse — cohort retention, RFM segmentation, window-function aggregations — to explain KPI movements
Core events
| Event | Trigger | Key properties |
|---|---|---|
page_viewed |
Page load | page_path, page_title |
user_signed_up |
Registration | method, referral_code |
product_viewed |
Product page | product_id, category, price |
checkout_started |
Checkout init | cart_value, item_count |
order_completed |
Purchase | order_id, value, items |
Expected output
- Analytics setup (GA4, Mixpanel, or Posthog)
- Documented tracking plan
- Core events implemented
- KPI dashboard configured
- Analytical SQL queries (cohort, RFM, window functions) when KPIs need root-cause analysis
Guidelines
- IMPORTANT: Revenue events always server-side
- NEVER track personal data without consent
- IMPORTANT: Consistent naming convention
[Object]_[Action] - YOU MUST configure RGPD consent before tracking
- IMPORTANT: Profile data (missing values, duplicates) before drawing conclusions from analytical queries
Think hard about the metrics that really matter.
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 · 49 lines · 31 tokens per session scan A a734fe9f4705
growth-analytics is an agent published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 469 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
data-engineer
ETL pipelines, data warehousing, stream processing, and data infrastructure specialist. Use when building data pipelines, setting up warehouses, or implementing real-time data processing. Trigger phrases: ETL, pipeline, data warehouse, BigQuery, Snowflake, Redshift, Kafka, Airflow, dbt, streaming, data lake, data…
database-expert
Expert database architect and engineer for PostgreSQL, MongoDB, Redis, and all major databases. Use when designing schemas, optimizing queries, planning migrations, implementing caching, or troubleshooting database performance.
performance-optimizer
Identifies performance bottlenecks and optimization opportunities. Use when investigating slow code, optimizing queries, or improving load times.
database-cloud-optimization-database-architect
Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures. Masters SQL/NoSQL/TimeSeries database selection, normalization strategies, migration planning, and performance-first design. Handles both greenfield architectures and…
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…