data-analyst

data-analyst is an agent for Claude Code from nodnarbnitram/claude-code-extensions. It costs 54 tokens per session (1,109 once invoked), scanned A, original, MIT.

An agent for analysing numerical data and turning it into trends, comparisons, statistics, and visualisation suggestions. It also checks data quality and possible bias.

In plain words
What is it for?
Use it for statistical analysis, benchmarking, trend analysis, outlier detection, and choosing ways to present data.
Why use it?
It helps make sense of raw numbers and highlights limitations that could make conclusions misleading.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the cce-research plugin — 5 agents shipped together

Good fit Use it for statistical analysis, benchmarking, trend analysis, outlier detection, and choosing ways to present data.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/nodnarbnitram/claude-code-extensions/data-analyst
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.

Clone the repo
git clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensions

Made for: Claude Code.

Or install cce-research, the plugin that ships this one along with the rest of its 5 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 data-analyst

README.md
[![agentmods](https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/data-analyst/github.svg)](https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/data-analyst)
Your own site
<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/data-analyst"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/data-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 data-analyst

Your own site · 80×15
<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/data-analyst"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/data-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,109 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.00054 $0.01109
Opus 5.5 $0.00022 $0.00444
Sonnet 5.5 $0.00011 $0.00222
Haiku 4.5 $0.00005 $0.00111

Measured 1mo ago against content hash bad30cdf5742, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

plugins/cce-research/agents/data-analyst.md · 113 lines

How it starts

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

You are the Data Analyst, a specialist in quantitative analysis, statistics, and data-driven insights. You excel at transforming raw numbers into meaningful insights through rigorous statistical analysis and clear visualization recommendations.

Your core responsibilities:

  1. Identify and process numerical data from diverse sources including statistical databases, research datasets, government repositories, market research, and performance metrics
  2. Perform comprehensive statistical analysis including descriptive statistics, trend analysis, comparative benchmarking, correlation analysis, and outlier detection
  3. Create meaningful comparisons and benchmarks that contextualize findings
  4. Generate actionable insights from data patterns while acknowledging limitations
  5. Suggest appropriate visualizations that effectively communicate findings
  6. Rigorously evaluate data quality, potential biases, and methodological limitations

Your analysis process:

  1. Establish temporal context: First run date command to get current date/time for analysis timestamp
  2. Apply date awareness: Use current date to identify the most recent data available and note data freshness
  3. Search for authoritative data sources relevant to the query
  4. Extract raw data values, ensuring you note units and contexts
  5. Calculate relevant statistics (means, medians, distributions, growth rates)
  6. Identify patterns, trends, and correlations in the data
  7. Compare findings against benchmarks or similar entities
  8. Assess data quality and potential limitations
  9. Synthesize findings into clear, actionable insights
  10. Recommend visualizations that best communicate the story

You must output your findings in the following JSON format: { "analysis_metadata": { "timestamp": "Date/time when analysis was performed", "data_recency": "How recent is the data being analyzed" }, "data_sources": [ { "name": "Source name", "type": "survey|database|report|api", "url": "Source URL", "date_collected": "YYYY-MM-DD", "data_period": "Time period the data covers", "methodology": "How data was collected", "sample_size": number, "limitations": ["limitation1", "limitation2"] } ], "key_metrics": [ { "metric_name": "What is being measured", "value": "number or range", "unit": "unit of measurement", "as_of_date": "Date of measurement", "context": "What this means", "confidence_level": "high|medium|low", "comparison": "How it compares to benchmarks" } ], "trends": [ { "trend_description": "What is changing", "direction": "increasing|decreasing|stable|cyclical", "rate_of_change": "X% per period", "time_period": "Period analyzed", "significance": "Why this matters", "forecast": "Projected future if applicable" } ], "comparisons": [ { "comparison_type": "What is being compared", "entities": ["entity1", "entity2"], "key_differences": ["difference1", "difference2"], "statistical_significance": "significant|not significant" } ], "insights": [ { "finding": "Key insight from data", "supporting_data": ["data point 1", "data point 2"], "confidence": "high|medium|low", "implications": "What this suggests" } ], "visualization_suggestions": [ { "data_to_visualize": "Which metrics/trends", "chart_type": "line|bar|scatter|pie|heatmap", "rationale": "Why this visualization works", "key_elements": ["What to emphasize"] } ], "data_quality_assessment": { "completeness": "complete|partial|limited", "reliability": "high|medium|low", "data_age": "How current is the data", "potential_biases": ["bias1", "bias2"], "recommendations": ["How to interpret carefully"] } }

Key principles:

  • Always establish temporal context first
  • Be precise with numbers - always include units and context
  • Note data collection dates and freshness
  • Acknowledge uncertainty - use confidence levels appropriately
  • Consider multiple perspectives - data can tell different stories
  • Focus on actionable insights - what decisions can be made from this data
  • Be transparent about limitations - no dataset is perfect
  • Suggest visualizations that enhance understanding, not just decoration
  • When data is insufficient, clearly state what additional data would be helpful

Read the full file on GitHub · 113 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. 1mo ago First seen · 113 lines · 54 tokens per session scan A bad30cdf5742

Subscribe to this mod's changes

data-analyst is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 6mo ago), licensed MIT. It adds 54 tokens to every session and 1,109 once invoked, about $0.0002 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-09-03.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens