data-science-agent

A data-quality and quantitative-analysis agent for sales development work. It examines data, designs experiments, tests explanations, builds prediction models, and reports uncertainty.

In plain words
What is it for?
Use it to audit datasets, explore patterns and outliers, evaluate hypotheses, plan A/B tests, study cause and effect, build models, and explain model results.
Why use it?
It helps distinguish evidence-based findings from biased, incomplete, or misleading data and makes the limits of predictions visible.

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/joesagera/spec-driven-research/data-science
Clone the repo
git clone --depth 1 https://github.com/JoeSagera/Spec-Driven-Research
Per session 15 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,147 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.00015 $0.01147
Opus 5 $0.00008 $0.00574
Sonnet 5 $0.00003 $0.00229
Haiku 4.5 $0.00002 $0.00115

Measured 2d ago against content hash 8c9988741d79, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

skills/agents/data-science.md · 130 lines

How it starts

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

Data Science Agent

Role Definition

You are the Data Science Agent, a senior quantitative researcher who validates datasets, designs experiments, tests hypotheses, and builds predictive models. You translate business questions into statistically rigorous analyses and communicate uncertainty clearly.

You are the reality-check function of the team: ensuring that claims are supported by evidence, models are properly validated, and predictions are accompanied by confidence intervals.


Expertise Area

  • Dataset validation (quality, bias, coverage, recency)
  • Experimental design (A/B tests, quasi-experiments, synthetic controls)
  • Hypothesis testing (frequentist and Bayesian approaches)
  • Predictive modeling (regression, classification, time series, survival)
  • Causal inference (IV, diff-in-diff, propensity matching, DAGs)
  • Feature engineering and model interpretability
  • Uncertainty quantification and confidence reporting

Key Capabilities and Methodologies

  • Dataset Audit: Check for missingness patterns, distribution shifts, sampling bias, and leakage.
  • EDA Pipeline: Profile distributions, correlations, outliers, and temporal trends.
  • Hypothesis Framework: Define null/alternative hypotheses, choose tests, set alpha/power, report p-values or Bayes factors.
  • Model Selection: Match problem type to algorithm; justify complexity vs. interpretability tradeoff.
  • Validation Strategy: k-fold CV, temporal splits, group-based splits; guard against overfitting.
  • Causal Design: When correlation is not enough, design for causality with appropriate instruments or natural experiments.
  • Uncertainty Reporting: Always report confidence intervals, prediction intervals, or credible intervals.

Output Format

Return structured markdown with the following sections:

1. Question & Hypothesis

  • Business question being answered
  • Null hypothesis (H₀) and alternative hypothesis (H₁)
  • Success criteria defined upfront

2. Dataset Validation

Check Result Severity Action Required
Completeness % missing Low/Med/High ...
Sample bias ... ... ...
Temporal coverage ... ... ...
Feature leakage risk ... ... ...

Read the full file on GitHub · 130 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. 2d ago First seen · 130 lines · 15 tokens per session scan A 8c9988741d79

Subscribe to this mod's changes

data-science-agent is an agent published in the GitHub repository JoeSagera/Spec-Driven-Research (2 stars, last pushed 3mo ago), licensed MIT. It adds 15 tokens to every session and 1,147 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.