feature-engineering

feature-engineering is a skill for Claude Code from zpower426/datapowers. It costs 24 tokens per session (2,430 once invoked), scanned A, original, MIT.

A method for turning raw data into inputs a machine-learning model can use. It requires transformations to be reproducible, checked, and kept separate from information the model is meant to predict.

In plain words
What is it for?
Use it to split data before transformations, create numeric, categorical, date, or text features, build pipelines, validate outputs, and document each feature.
Why use it?
It prevents target leakage and inconsistent processing, which can make evaluation unreliable or cause training and production data to be handled differently.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the datapowers plugin — 20 skills, 3 commands, 3 agents, 1 hook shipped together

Good fit Use it to split data before transformations, create numeric, categorical, date, or text features, build pipelines, validate outputs, and document each feature.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zpower426/datapowers/feature-engineering
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 zpower426/datapowers --skill feature-engineering
Clone the repo
git clone --depth 1 https://github.com/zpower426/datapowers

Made for: Claude Code.

Or install datapowers, the plugin that ships this one along with the rest of its 20 skills, 3 commands, 3 agents, 1 hook.

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 feature-engineering

README.md
[![agentmods](https://agentmods.dev/badge/skills/zpower426/datapowers/feature-engineering/github.svg)](https://agentmods.dev/skills/zpower426/datapowers/feature-engineering)
Your own site
<a href="https://agentmods.dev/skills/zpower426/datapowers/feature-engineering"><img src="https://agentmods.dev/badge/skills/zpower426/datapowers/feature-engineering/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 feature-engineering

Your own site · 80×15
<a href="https://agentmods.dev/skills/zpower426/datapowers/feature-engineering"><img src="https://agentmods.dev/badge/skills/zpower426/datapowers/feature-engineering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,430 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.00024 $0.02430
Opus 5.5 $0.00010 $0.00972
Sonnet 5.5 $0.00005 $0.00486
Haiku 4.5 $0.00002 $0.00243

Measured 2mo ago against content hash a8a8ea4f67ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

feature-engineering 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 2mo 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/feature-engineering/SKILL.md · 247 lines

How it starts

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

Feature Engineering

Systematic transformation of raw data into model-ready features. Every step must be reproducible, leakage-free, and validated.

Iron Law: NO FEATURES DERIVED FROM THE TARGET VARIABLE. NO TRANSFORMERS FIT ON THE FULL DATASET.

Checklist

  1. Confirm EDA and validation completed — check for EDA report and validation gate decision
  2. Establish train/test split — before any transformation
  3. Audit leakage candidates — review flags from EDA, remove or justify each
  4. Plan transformations by feature type — numeric, categorical, datetime, text
  5. Implement transformations with Pipelines — scikit-learn Pipeline or similar
  6. Fit transformers on training data only — persist fitted objects
  7. Validate post-transform schema — run data-validation on output
  8. Log feature registry — document every feature: business motivation, transformation, MI score, leakage status
  9. Run feature importance check — flag unexpectedly dominant features

Train/Test Split First

from sklearn.model_selection import train_test_split

# ALWAYS split before ANY transformation
X_train, X_test, y_train, y_test = train_test_split(
    df.drop(columns=[target]),
    df[target],
    test_size=0.2,
    random_state=42,        # REQUIRED: document seed
    stratify=df[target] if is_classification else None
)

print(f"Train: {len(X_train)} rows | Test: {len(X_test)} rows")
print(f"Train target distribution:\n{y_train.value_counts(normalize=True)}")
print(f"Test target distribution:\n{y_test.value_counts(normalize=True)}")

For time-series data: Split by time, NEVER randomly.

cutoff_date = df['date'].quantile(0.8)
train = df[df['date'] < cutoff_date]
test  = df[df['date'] >= cutoff_date]

Read the full file on GitHub · 247 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. 2mo ago First seen · 247 lines · 24 tokens per session scan A a8a8ea4f67ef

Subscribe to this mod's changes

feature-engineering is a skill published in the GitHub repository zpower426/datapowers (1 stars, last pushed 7mo ago), licensed MIT. It adds 24 tokens to every session and 2,430 once invoked, about $0.0001 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-08-31.

Related

feature-engineering compared with skills from other repositories

feature-engineering next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
feature-engineeringzpower426/datapowersSkill17mo agoMITA24Claude Code
local-llmTserenTserenov/FMT-exocortex-templateSkill63todayMITA78Claude Code
llm-app-patternsdavila7/claude-code-templatesSkill33ktodayMITA54Claude Code, Codex
multimodal-blip-2davila7/claude-code-templatesSkill33ktodayMITA52Claude Code, Codex
post-training-grpo-rl-trainingdavila7/claude-code-templatesSkill33ktodayMITA28Claude Code, Codex
prompt-engineering-instructordavila7/claude-code-templatesSkill33ktodayMITA44Claude Code, Codex
emerging-techniques-knowledge-distillationdavila7/claude-code-templatesSkill33ktodayMITA70Claude Code, Codex