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-analyticsgit 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.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 | $0.00031 | $0.00469 |
| Opus 5 | $0.00015 | $0.00234 |
| Sonnet 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 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
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.
- 4d 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 today), licensed MIT. It adds 31 tokens to every session and 469 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
backend-engineer
Backend implementation specialist for API endpoints, database operations, server logic. Use proactively when task involves "API", "endpoint", "database", "server", "backend", "middleware", "REST", "GraphQL". Loads coding-standards, tdd, ralph-loop, vibe-coding skills.
database-migrations
Database Migration Safety Agent.
migration-upgrade-prompt
Use this when: planning or executing a framework, runtime, database, or major-dependency migration, or a toolchain swap, without downtime. Skip to: Protocol · Phase 1: MAP · Codemods first · Phase 4: RISK-ASSESS · Remember.
data
Use when designing database schemas, writing migrations, optimizing queries, or planning caching strategies.
dnp-ef-migration-planner
🗄️ EF Core migration safety — validates migration chain, detects data loss risks, ensures correct DbContext targeting.
db-executor
Internal dynos-work agent. Implements schema changes, migrations, ORM models, and queries. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.