analytics-reporter

An agent for examining analytics data, finding patterns, and turning results into performance reports and recommendations. Analytics are measurements such as visits, sales, or engagement.

In plain words
What is it for?
Use it for metric analysis, insight generation, performance reviews, and data-based recommendations.
Why use it?
It helps turn raw measurements into an understandable account of what happened and what may need attention. The supplied description does not specify particular data sources or metrics.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add ccplugins/awesome-claude-code-plugins
agentmods
npx agentmods add plugins/ccplugins/awesome-claude-code-plugins/analytics-reporter
Clone the repo
git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

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

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/analytics-reporter/.claude-plugin/plugin.json · 9 lines

What it actually says

{
  "name": "analytics-reporter",
  "description": "Use this agent when analyzing metrics, generating insights from data, creating performance reports, or making data-driven recommendations. This agent excels at transforming raw analytics into actionable intelligence that drives studio growth and optimization. Examples:\\n\\n<example>\\nContext: Monthly performance review needed",
  "version": "1.0.0",
  "author": {
    "name": "Michael Galpert"
  },
  "homepage": "https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/analytics-reporter"
}
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. yesterday First seen · 9 lines scan A fbd722c44556

Subscribe to this mod's changes

analytics-reporter is a plugin published in the GitHub repository ccplugins/awesome-claude-code-plugins (926 stars, last pushed 19d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.