eda-and-data-profiling

eda-and-data-profiling is a skill for Claude Code, Codex from makifbaysal/tasktrooper. It costs 61 tokens per session (1,359 once invoked), scanned A, original, Apache-2.0.

A method for inspecting a new dataset, table, file, or data source before using it in a feature or model.

In plain words
What is it for?
Use it to check data shape, uniqueness, time coverage, freshness, column roles, and class balance, then record the findings as checks or assumptions.
Why use it?
It reveals incorrect assumptions about rows, keys, missing values, dates, duplicates, and other data problems before they spread.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to check data shape, uniqueness, time coverage, freshness, column roles, and class balance, then record the findings as checks or assumptions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/makifbaysal/tasktrooper/eda-and-data-profiling
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.

Any agent
npx skills add makifbaysal/tasktrooper --skill eda-and-data-profiling
Clone the repo
git clone --depth 1 https://github.com/makifbaysal/tasktrooper

Made for: Claude Code, Codex.

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 eda-and-data-profiling

README.md
[![agentmods](https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/eda-and-data-profiling/github.svg)](https://agentmods.dev/skills/makifbaysal/tasktrooper/eda-and-data-profiling)
Your own site
<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/eda-and-data-profiling"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/eda-and-data-profiling/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 eda-and-data-profiling

Your own site · 80×15
<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/eda-and-data-profiling"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/eda-and-data-profiling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,359 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.00061 $0.01359
Opus 5.5 $0.00024 $0.00544
Sonnet 5.5 $0.00012 $0.00272
Haiku 4.5 $0.00006 $0.00136

Measured 4d ago against content hash 461bbce9bd12, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

eda-and-data-profiling 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 4d 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.

catalog/agents/data-scientist/skills/eda-and-data-profiling/SKILL.md · 107 lines

How it starts

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

EDA and Data Profiling

Overview

Exploration answers "what is actually in this data?" before anything is built on it. In this role exploration has a deliverable: the facts you learn become a schema, a test or a documented assumption in the repository — not a notebook cell nobody re-runs.

Core principle: every surprise you find in EDA ends up as a check that would catch it next time (data-validation-contracts) or a written assumption in your closing message.

1. Structure first

Answer these before looking at any distribution:

  • Grain: one row is one what? (an order, an order line, a customer-day)
  • Key: which column(s) identify a row — and are they actually unique?
  • Size and span: row count, earliest and latest timestamp, any missing days.
  • Freshness: when was it last updated; is the latest period complete?
  • Column roles: identifier, dimension, metric, timestamp, free text, boolean, nested.
def assert_grain(df: pd.DataFrame, key: list[str]) -> None:
    dupes = df.duplicated(subset=key, keep=False)
    if dupes.any():
        raise ValueError(f"{int(dupes.sum())} rows share a {key} key, e.g. {df.loc[dupes, key].head(3).to_dict('records')}")

2. Profile every column

Column kind Look at
All null rate, distinct count, cardinality ratio, top and bottom values
Numeric min, p1, p25, median, mean, p75, p99, max; zeros; negatives where impossible
String / category empty strings, whitespace, case variants ("US", "us", "USA"), unexpected categories
Timestamp min/max, future dates, gaps per day/week, timezone (naive vs aware)
Target class balance or distribution, by time period

Fast paths:

duckdb.sql("SUMMARIZE SELECT * FROM 'data/events/*.parquet'").df()
def profile(df: pd.DataFrame) -> pd.DataFrame:
    return pd.DataFrame({
        "dtype": df.dtypes.astype(str),
        "null_rate": df.isna().mean(),
        "n_unique": df.nunique(dropna=True),
        "example": df.apply(lambda s: s.dropna().iloc[0] if s.notna().any() else None),
    })

Read the full file on GitHub · 107 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. 4d ago First seen · 107 lines · 61 tokens per session scan A 461bbce9bd12

Subscribe to this mod's changes

eda-and-data-profiling is a skill published in the GitHub repository makifbaysal/tasktrooper (113 stars, last pushed yesterday), licensed Apache-2.0. It adds 61 tokens to every session and 1,359 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-10-09.