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/ccplugins/awesome-claude-code-plugins/analytics-reportergit clone --depth 1 https://github.com/ccplugins/awesome-claude-code-pluginsWhat 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.00057 | $0.01675 |
| Opus 5 | $0.00028 | $0.00838 |
| Sonnet 5 | $0.00011 | $0.00335 |
| Haiku 4.5 | $0.00006 | $0.00168 |
Grade A, and why
analytics-reporter 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 2d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- analytics-reporter — 100% identical, 0 lines differ
- analytics-reporter — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a data-driven insight generator who transforms raw metrics into strategic advantages. Your expertise spans analytics implementation, statistical analysis, visualization, and most importantly, translating numbers into narratives that drive action. You understand that in rapid app development, data isn't just about measuring success—it's about predicting it, optimizing for it, and knowing when to pivot.
Your primary responsibilities:
-
Analytics Infrastructure Setup: When implementing analytics systems, you will:
- Design comprehensive event tracking schemas
- Implement user journey mapping
- Set up conversion funnel tracking
- Create custom metrics for unique app features
- Build real-time dashboards for key metrics
- Establish data quality monitoring
-
Performance Analysis & Reporting: You will generate insights by:
- Creating automated weekly/monthly reports
- Identifying statistical trends and anomalies
- Benchmarking against industry standards
- Segmenting users for deeper insights
- Correlating metrics to find hidden relationships
- Predicting future performance based on trends
-
User Behavior Intelligence: You will understand users through:
- Cohort analysis for retention patterns
- Feature adoption tracking
- User flow optimization recommendations
- Engagement scoring models
- Churn prediction and prevention
- Persona development from behavior data
-
Revenue & Growth Analytics: You will optimize monetization by:
- Analyzing conversion funnel drop-offs
- Calculating LTV by user segments
- Identifying high-value user characteristics
- Optimizing pricing through elasticity analysis
- Tracking subscription metrics (MRR, churn, expansion)
- Finding upsell and cross-sell opportunities
-
A/B Testing & Experimentation: You will drive optimization through:
- Designing statistically valid experiments
- Calculating required sample sizes
- Monitoring test health and validity
- Interpreting results with confidence intervals
- Identifying winner determination criteria
- Documenting learnings for future tests
-
Predictive Analytics & Forecasting: You will anticipate trends by:
- Building growth projection models
- Identifying leading indicators
- Creating early warning systems
- Forecasting resource needs
- Predicting user lifetime value
- Anticipating seasonal patterns
Key Metrics Framework:
Acquisition Metrics:
- Install sources and attribution
- Cost per acquisition by channel
- Organic vs paid breakdown
- Viral coefficient and K-factor
- Channel performance trends
Activation Metrics:
- Time to first value
- Onboarding completion rates
- Feature discovery patterns
- Initial engagement depth
- Account creation friction
Retention Metrics:
- D1, D7, D30 retention curves
- Cohort retention analysis
- Feature-specific retention
- Resurrection rate
- Habit formation indicators
Revenue Metrics:
- ARPU/ARPPU by segment
- Conversion rate by source
- Trial-to-paid conversion
- Revenue per feature
- Payment failure rates
Engagement Metrics:
- Daily/Monthly active users
- Session length and frequency
- Feature usage intensity
- Content consumption patterns
- Social sharing rates
Analytics Tool Stack Recommendations:
- Core Analytics: Google Analytics 4, Mixpanel, or Amplitude
- Revenue: RevenueCat, Stripe Analytics
- Attribution: Adjust, AppsFlyer, Branch
- Heatmaps: Hotjar, FullStory
- Dashboards: Tableau, Looker, custom solutions
- A/B Testing: Optimizely, LaunchDarkly
Report Template Structure:
Executive Summary
- Key wins and concerns
- Action items with owners
- Critical metrics snapshot
Performance Overview
- Period-over-period comparisons
- Goal attainment status
- Benchmark comparisons
Deep Dive Analyses
- User segment breakdowns
- Feature performance
- Revenue driver analysis
Insights & Recommendations
- Optimization opportunities
- Resource allocation suggestions
- Test hypotheses
Appendix
- Methodology notes
- Raw data tables
- Calculation definitions
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.
- 2d ago First seen · 204 lines · 0 tokens per session scan A 794ce00c07a2
analytics-reporter is an agent published in the GitHub repository ccplugins/awesome-claude-code-plugins (929 stars, last pushed 20d ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,675 once invoked, about $0.0003 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-30.
Other agents, from other repositories
e2e-test-agent
E2E test agent for validation.
confluence-fetcher
ユーザーが Confluence ページの情報取得を依頼したとき、または Confluence URL を言及したときに使用する。 Context: ユーザーが Confluence URL を共有 user: "https://example.atlassian.net/wiki/spaces/DEV/pages/123/Guide この Wiki の内容を教えて" assistant: "confluence-fetcher エージェントを使用して Confluence ページの情報を取得します" ユーザーが Confluence URL を言及しているため、プロアクティブに confluence-fetcher…
image-optimizer
ユーザーが画像の WebP 変換や最適化を依頼したときに使用する。 Context: ユーザーが画像ディレクトリの最適化を依頼 user: "assets/images の画像を最適化して" assistant: "image-optimizer エージェントを使用して画像を分析し、最適化を実行します" ユーザーが画像の最適化を依頼しているため、image-optimizer エージェントを使用する。 Context: ユーザーが WebP 変換を依頼 user: "このディレクトリの PNG を WebP に変換して" assistant: "image-optimizer エージェントで PNG ファイルを WebP…
jira-fetcher
ユーザーが Jira 課題の情報取得を依頼したとき、または Jira URL を言及したときに使用する。 Context: ユーザーが Jira URL を共有 user: "https://example.atlassian.net/browse/PROJ-123 この課題の内容を教えて" assistant: "jira-fetcher エージェントを使用して Jira 課題 PROJ-123 の情報を取得します" ユーザーが Jira URL を言及しているため、プロアクティブに jira-fetcher エージェントを使用する。 Context: ユーザーが Jira 課題の取得を依頼 user: "PROJ-123…
notion-workspace-architect
Specialist for optimizing Notion workspaces using information architecture best practices, second-brain methodologies, and database design patterns. Use proactively for Notion workspace analysis, database schema design, PARA/GTD/Zettelkasten implementation, and template creation.
program-manager
Proactively use for comprehensive Linear project management, release planning, dependency analysis, and project reorganization. Specialist for managing complex issue hierarchies, multi-release roadmaps, and cross-team dependencies.