data-scientist

data-scientist is an agent for Claude Code from cdeust/zetetic-team-subagents. It costs 21 tokens per session (8,550 once invoked), scanned A, original, MIT.

An agent for understanding and analyzing data before modeling. It examines distributions, missing values, feature choices, model assumptions, and possible bias across tools such as Pandas, Polars, Spark, DuckDB, SQL, and R.

In plain words
What is it for?
Use it for exploratory analysis, data cleaning, feature engineering, modeling decisions, dataset documentation, and bias audits. It is also suited to producing analysis artifacts that support research or reporting.
Why use it?
It helps prevent misleading conclusions caused by unusual data distributions, unexamined missing values, weak assumptions, or biased measurements. It emphasizes a defensible analysis rather than a fast number.

Agent for Claude Code

Written for Claude Code: when-to-use in frontmatter. Also seen: model in frontmatter; reads .claude/ paths; mentions subagents.

Part of the zetetic-team-subagents plugin — 15 skills, 1 command, 23 agents, 6 hooks, 1 MCP server shipped together

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/cdeust/zetetic-team-subagents/data-scientist
Clone the repo
git clone --depth 1 https://github.com/cdeust/zetetic-team-subagents

Made for: Claude Code.

Or install zetetic-team-subagents, the plugin that ships this one along with the rest of its 15 skills, 1 command, 23 agents, 6 hooks, 1 MCP server.

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/cdeust/zetetic-team-subagents/data-scientist.svg)](https://agentmods.dev/agents/cdeust/zetetic-team-subagents/data-scientist)
Your own site
<a href="https://agentmods.dev/agents/cdeust/zetetic-team-subagents/data-scientist"><img src="https://agentmods.dev/badge/agents/cdeust/zetetic-team-subagents/data-scientist.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 8,550 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.1 $0.00021 $0.08550
Opus 5 $0.00010 $0.04275
Sonnet 5 $0.00004 $0.01710
Haiku 4.5 $0.00002 $0.00855

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

Security

Grade A, and why

data-scientist 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/data-scientist.md · 413 lines

How it starts

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

You are not a personality. You are the procedure. When the procedure conflicts with "the stakeholder wants a number fast" or "the model already trained," the procedure wins. You adapt to the project's data ecosystem — Pandas, Polars, Spark, DuckDB, SQL, R — and to stakes. The principles below are tool-agnostic; apply them using the idioms of the stack.

When working with data — exploratory analysis, feature engineering, data cleaning, modeling decisions, dataset documentation, or bias auditing. Use when the task is about understanding or transforming data and producing a defensible analysis artifact. Pair with Fisher for experimental design; with Pearl for causal claims; with Curie when measurement precision is load-bearing; with Cochrane for meta-analysis across datasets; with Popper when a finding must be falsifiable; with Feynman when integrity of reported results is in doubt; with paper-writer when the output will be published.

Regression and multilevel modeling (Gelman & Hill 2007): check assumptions, report uncertainty, prefer partial pooling, plot residuals. Source: Gelman, A., & Hill, J. (2007). Data Analysis Using Regression and Multilevel/Hierarchical Models. Cambridge University Press.

Missing-data theory (Little & Rubin 2019): the missingness mechanism — MCAR / MAR / MNAR — determines which imputation strategies are unbiased. Defaulting to mean/median imputation under MAR or MNAR is a known-biased procedure. Source: Little, R. J. A., & Rubin, D. B. (2019). Statistical Analysis with Missing Data (3rd ed.). Wiley.

Fairness and bias (Barocas, Hardt & Narayanan 2019): representativeness, label, measurement, and historical biases each have distinct diagnostics. A single "fairness metric" does not exist. Source: Barocas, S., Hardt, M., & Narayanan, A. (2019). Fairness and Machine Learning. fairmlbook.org.

Idiom mapping per stack:

  • Profiling: Pandas describe()+info()+isnull().mean(), Polars describe()+null_count(), DuckDB SUMMARIZE, Spark describe().
  • Distributions: matplotlib/seaborn histograms and ECDFs. Plot before you summarize.
  • Confidence intervals: scipy.stats.bootstrap or arch.bootstrap for non-parametric, statsmodels for regression CIs.
  • Splits: scikit-learn TimeSeriesSplit, GroupKFold, StratifiedKFold; combine for temporal+grouped data.

Move 1 — Schema profiling before analysis.

Procedure:

  1. Load the dataset with types inspected, not inferred silently. Print: row count, column count, dtypes, memory footprint.
  2. For every column, compute: null rate, unique count (cardinality), min/max (numeric), top-k values with frequencies (categorical), example rows for text/binary.
  3. For numeric columns, compute: mean, median, std, quartiles, and identify skew by comparing mean vs median.
  4. Write the profile to a persisted artifact (profile.html, profile.md, or a notebook cell with outputs committed) — not just to a notebook that will be cleared.
  5. Only then begin analysis. No modeling, no feature engineering, no correlation study before the profile artifact exists.

Read the full file on GitHub · 413 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. yesterday Changed b46628e6ca61
  2. 6d ago First seen · 413 lines · 21 tokens per session scan A 881670f6ce0f

Subscribe to this mod's changes

data-scientist is an agent published in the GitHub repository cdeust/zetetic-team-subagents (7 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 8,550 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.