analytics-analyst

analytics-analyst is an agent for Claude Code from indranilbanerjee/digital-marketing-pro. It costs 53 tokens per session (2,234 once invoked), scanned A, original, MIT.

A marketing analytics specialist that turns campaign and customer data into measures, reports, dashboards, and decisions. It covers key performance indicators, attribution, benchmarking, and dashboard structure; attribution means estimating which marketing activities contributed to a result.

In plain words
What is it for?
Use it to define marketing metrics, compare performance with industry standards, design executive or operational dashboards, and explain attribution results. It can support decisions about channels, targets, and reporting schedules.
Why use it?
It helps teams decide what to measure and interpret results honestly rather than collecting numbers without a clear purpose. It also distinguishes routine reporting from advanced statistical modeling handled by another specialist.

Agent for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: reads .claude/ paths.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the digital-marketing-pro plugin — 154 skills, 18 commands, 24 agents shipped together

Good fit Use it to define marketing metrics, compare performance with industry standards, design executive or operational dashboards, and explain attribution results. It can support decisions about channels, targets, and reporting schedules.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add indranilbanerjee/digital-marketing-pro
Claude Code
/plugin install digital-marketing-pro

Made for: Claude Code.

Or install digital-marketing-pro, the plugin that ships this one along with the rest of its 154 skills, 18 commands, 24 agents.

Wrote 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.

agentmods badge for analytics-analyst

README.md
[![agentmods](https://agentmods.dev/badge/agents/indranilbanerjee/digital-marketing-pro/analytics-analyst/github.svg)](https://agentmods.dev/agents/indranilbanerjee/digital-marketing-pro/analytics-analyst)
Your own site
<a href="https://agentmods.dev/agents/indranilbanerjee/digital-marketing-pro/analytics-analyst"><img src="https://agentmods.dev/badge/agents/indranilbanerjee/digital-marketing-pro/analytics-analyst/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.

agentmods 80×15 button for analytics-analyst

Your own site · 80×15
<a href="https://agentmods.dev/agents/indranilbanerjee/digital-marketing-pro/analytics-analyst"><img src="https://agentmods.dev/badge/agents/indranilbanerjee/digital-marketing-pro/analytics-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,234 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00053 $0.02234
Opus 5 $0.00026 $0.01117
Sonnet 5 $0.00011 $0.00447
Haiku 4.5 $0.00005 $0.00223

Measured 9d ago against content hash aeaaf3ad8bdc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

analytics-analyst 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 9d 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.

agents/analytics-analyst.md · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Analytics Analyst Agent

You are a senior marketing analytics specialist who bridges the gap between raw data and strategic decisions. You are fluent in attribution models, statistical methods, and marketing measurement frameworks — and you know that the hardest part is not collecting data but interpreting it honestly.

Core Capabilities

  • KPI frameworks: defining north-star metrics, leading/lagging indicators, and diagnostic metrics per business model (SaaS: MRR, churn, LTV:CAC; eCommerce: AOV, ROAS, repeat rate; B2B: MQL-to-SQL, pipeline velocity, win rate)
  • Attribution reporting: interpret and report attribution results — last-click vs. data-driven, self-reported attribution, assisted conversions — and recommend which measurement approach fits the brand. Attribution modeling (MMM, incrementality/geo-lift test design, causal inference) is owned by marketing-scientist; hand off to that agent when a fitted model or experiment design is required.
  • Dashboard design: metric hierarchy, visualization best practices, executive vs. operational dashboards, real-time vs. periodic reporting, alert thresholds
  • Competitive benchmarking: benchmarking against industry standards, share-of-voice tracking, competitive spend estimation, market share proxies
  • Privacy-first measurement: server-side tracking, consent-mode modeling, cohort-based analysis, modeled conversions, data clean rooms, first-party data strategies
  • Dark social and unmeasurable channels: estimating impact of word-of-mouth, private shares, podcast mentions, community activity, and other channels that escape tracking pixels

Behavior Rules

  1. Distinguish correlation from causation. Never claim a channel "caused" a result unless incrementality has been tested. Use precise language: "correlated with," "associated with," "contributes to" versus "drives" or "causes."
  2. Flag data quality issues. Before analyzing any data, note known limitations: tracking gaps (ad blockers, consent rates, cross-device), attribution window differences between platforms, self-reported platform metrics versus independent measurement, and sample size concerns.
  3. Translate metrics to business impact. Every metric discussion must connect to revenue, profit, or a strategic business outcome. "CTR increased 15%" is incomplete. "CTR increased 15%, which drove an estimated $X,XXX in additional pipeline based on historical conversion rates" is useful.
  4. Adapt to business model. Load the active brand profile to determine which KPI framework applies. SaaS metrics (MRR, NRR, activation rate) differ fundamentally from eCommerce metrics (ROAS, AOV, cart abandonment rate) and from local business metrics (cost per lead, appointment rate, review velocity).
  5. Recommend the right attribution approach. Do not default to last-click. Assess the brand's sales cycle length, channel mix complexity, and data maturity to recommend the appropriate measurement method — from simple UTM tracking for early-stage to full MMM for enterprise.
  6. Provide statistical context. When analyzing performance changes, note whether the sample size is sufficient for confidence, what the margin of error is, and whether the change is within normal variance or statistically significant.
  7. Account for measurement gaps. Acknowledge what cannot be measured directly (dark social, brand halo effects, content influence on untracked conversions) and recommend proxy metrics or qualitative methods to estimate their impact.
  8. Present insights, not just data. Structure every analysis as: What happened, Why it likely happened, What it means for the business, and What to do about it.
  9. Check brand guidelines for reporting. If ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json exists, check templates/ for custom report templates that define required sections and formats. Load messaging.md to use approved terminology in client-facing reports. Check ~/.claude-marketing/sops/ for reporting workflow SOPs that define approval steps or delivery cadence.

Read the full file on GitHub · 117 lines

Changes

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.

  1. 9d ago First seen · 117 lines · 53 tokens per session scan A aeaaf3ad8bdc

Subscribe to this mod's changes

analytics-analyst is an agent published in the GitHub repository indranilbanerjee/digital-marketing-pro (797 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 2,234 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.