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.
npx agentmods add skills/zpower426/datapowers/feature-engineeringnpx skills add zpower426/datapowers --skill feature-engineeringgit clone --depth 1 https://github.com/zpower426/datapowersWrote 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.
[](https://agentmods.dev/skills/zpower426/datapowers/feature-engineering)<a href="https://agentmods.dev/skills/zpower426/datapowers/feature-engineering"><img src="https://agentmods.dev/badge/skills/zpower426/datapowers/feature-engineering.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00024 | $0.02430 |
| Opus 5 | $0.00012 | $0.01215 |
| Sonnet 5 | $0.00005 | $0.00486 |
| Haiku 4.5 | $0.00002 | $0.00243 |
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 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.
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
- Confirm EDA and validation completed — check for EDA report and validation gate decision
- Establish train/test split — before any transformation
- Audit leakage candidates — review flags from EDA, remove or justify each
- Plan transformations by feature type — numeric, categorical, datetime, text
- Implement transformations with Pipelines — scikit-learn Pipeline or similar
- Fit transformers on training data only — persist fitted objects
- Validate post-transform schema — run data-validation on output
- Log feature registry — document every feature: business motivation, transformation, MI score, leakage status
- 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]
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.
- 4d ago First seen · 247 lines · 24 tokens per session scan A a8a8ea4f67ef
feature-engineering is a skill published in the GitHub repository zpower426/datapowers (1 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 2,430 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.
Other skills, from other repositories
local-llm
Локальный LLM-стек на Mac (Apple Silicon, MLX) под приватность и запасной режим. NL-вход к установке/запуску/переключению моделей + слой суждения для мониторинга новых моделей. Тонкая обёртка над скриптами РП404, не замена.
llm-app-patterns
Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability.
blip-2-vision-language
Vision-language pre-training framework bridging frozen image encoders and LLMs. Use when you need image captioning, visual question answering, image-text retrieval, or multimodal chat with state-of-the-art zero-shot performance.
knowledge-distillation
Compress large language models using knowledge distillation from teacher to student models. Use when deploying smaller models with retained performance, transferring GPT-4 capabilities to open-source models, or reducing inference costs. Covers temperature scaling, soft targets, reverse KLD, logit distillation, and…
speculative-decoding
Accelerate LLM inference using speculative decoding, Medusa multiple heads, and lookahead decoding techniques. Use when optimizing inference speed (1.5-3.6× speedup), reducing latency for real-time applications, or deploying models with limited compute. Covers draft models, tree-based attention, Jacobi iteration…
pyvene-interventions
Provides guidance for performing causal interventions on PyTorch models using pyvene's declarative intervention framework. Use when conducting causal tracing, activation patching, interchange intervention training, or testing causal hypotheses about model behavior.