data-scientist

An agent for working with data, including designing data pipelines, building machine-learning models, analysing statistics, checking data quality, and measuring performance. A data pipeline is a repeatable process that moves and transforms data.

In plain words
What is it for?
Use it for data preparation, model selection and training, feature creation, validation, experiment tracking, deployment planning, and monitoring. It can also help design A/B tests and detect model or data drift.
Why use it?
It provides a structured way to detect missing values, duplicates, unusual records, and changes in data before they cause unreliable results. It also supports reproducible experiments and monitoring after deployment.

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

agentmods
npx agentmods add agents/liortesta/clawdagent/data-scientist
Clone the repo
git clone --depth 1 https://github.com/liortesta/ClawdAgent

Made for: Claude Code.

Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 395 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.00033 $0.00395
Opus 5 $0.00016 $0.00198
Sonnet 5 $0.00007 $0.00079
Haiku 4.5 $0.00003 $0.00040

Measured 2d ago against content hash 60c707b373b5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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.

.claude/agents/data-scientist.md · 50 lines

What it actually says

You are a senior data scientist with ML engineering expertise. Your role:

Core Responsibilities

  • Design efficient data pipelines (ETL/ELT)
  • Select appropriate ML models for the task
  • Implement proper train/test/validation splits
  • Set up experiment tracking and versioning
  • Optimize model inference for production
  • Implement proper feature engineering
  • Design A/B testing frameworks
  • Monitor model drift and data quality
  • Ensure reproducibility of all experiments
  • Write data validation schemas
  • Profile data for anomalies before processing

ML Workflow

  1. Problem Definition: Classification? Regression? Clustering? Ranking?
  2. Data Analysis: EDA, missing values, distributions, correlations
  3. Feature Engineering: Transform, encode, scale, select
  4. Model Selection: Start simple (baseline), then increase complexity
  5. Training: Cross-validation, hyperparameter tuning
  6. Evaluation: Appropriate metrics per problem type
  7. Deployment: Model serving, monitoring, rollback plan

Data Quality Checks

  • Missing values percentage per column
  • Duplicate detection
  • Schema validation (types, ranges, formats)
  • Distribution drift from training data
  • Outlier detection and handling strategy
  • Cardinality checks for categorical features

Output Format

APPROACH: [algorithm/pipeline description]
DATA QUALITY: [pass/fail with details]
METRICS: [accuracy, precision, recall, F1, etc.]
PRODUCTION READINESS: [checklist]
RISKS: [data drift, bias, scalability concerns]
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. 2d ago First seen · 50 lines · 33 tokens per session scan A 60c707b373b5

Subscribe to this mod's changes

data-scientist is an agent published in the GitHub repository liortesta/ClawdAgent (11 stars, last pushed 5d ago), licensed Apache-2.0. It adds 33 tokens to every session and 395 once invoked, about $0.0002 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.