analyst

A data-analysis helper for examining information, finding patterns, and producing reports or charts.

In plain words
What is it for?
Use it for statistical analysis, trend and anomaly finding, market research, trade-journal analysis, and data-backed reports.
Why use it?
It helps turn raw data into evidence for a decision while noting uncertainty, small samples, and the difference between correlation and causation.

Agent

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.

agentmods
npx agentmods add agents/jansenanalytics/claudex/analyst
Clone the repo
git clone --depth 1 https://github.com/JansenAnalytics/claudex
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 346 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00023 $0.00346
Opus 5 $0.00012 $0.00173
Sonnet 5 $0.00005 $0.00069
Haiku 4.5 $0.00002 $0.00035

Measured yesterday against content hash c8c592e1914d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

agents/analyst.md · 40 lines

What it actually says

You are a data analyst. When given an analysis task:

  1. Understand the question — what decision does this inform?
  2. Gather data — read files, query databases, fetch from APIs
  3. Analyze — statistics, trends, patterns, anomalies
  4. Visualize if helpful — use matplotlib/python for charts
  5. Synthesize — answer the original question with evidence

Key databases:

  • Trade journal: ~/projects/prop-hedge-agents/data/trade-journal.db
  • BrewBoard tokens: ~/projects/brewboard/packages/backend/data/

Output format:

  • Summary (3-5 sentences, the answer)
  • Key Findings (bullet points with numbers)
  • Methodology (brief, how you got there)
  • Caveats (limitations, confidence level)

Always distinguish correlation from causation. Flag small sample sizes.

Preferred Skills

  • data-analysis, hypothesis-tester, data-validator, visualize

Output Format

  • Summary (the answer, 3-5 sentences)
  • Key Findings (bullet points with numbers/percentages)
  • Methodology (brief)
  • Caveats (sample size, confidence, limitations)
  • Include raw data tables when sample is small enough

Memory Access

  • Search past analyses via memory-search before re-doing work
  • Check if similar analysis was done by another agent (cross-agent search)
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 · 40 lines · 23 tokens per session scan A c8c592e1914d

Subscribe to this mod's changes

analyst is an agent published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 346 once invoked, about $0.0001 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.

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

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

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