feature-store-and-ml-data-pipelines

feature-store-and-ml-data-pipelines is a skill for Claude Code, Codex from vaquarkhan/data-engineering-agent-skills. It costs 49 tokens per session (462 once invoked), scanned A, original, MIT.

Guidance for building machine-learning data pipelines and feature stores. A feature is an input value used by a machine-learning model, and a feature store manages those values for training and predictions.

In plain words
What is it for?
Use it when creating training datasets, reusable features, online or offline feature access, model-ready data products, or feature ownership and quality rules.
Why use it?
It helps keep training data historically correct and ensures the values used during training match those available when the model makes predictions. This reduces data leakage and training-serving mismatches.

Skill for Claude CodeCodex

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

Good fit Use it when creating training datasets, reusable features, online or offline feature access, model-ready data products, or feature ownership and quality rules.

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

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 feature-store-and-ml-data-pipelines

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/vaquarkhan/data-engineering-agent-skills/feature-store-and-ml-data-pipelines"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/feature-store-and-ml-data-pipelines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 462 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.00049 $0.00462
Opus 5 $0.00024 $0.00231
Sonnet 5 $0.00010 $0.00092
Haiku 4.5 $0.00005 $0.00046

Measured 12d ago against content hash b1c623fbd882, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

feature-store-and-ml-data-pipelines 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 12d 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-store-and-ml-data-pipelines/SKILL.md · 69 lines

How it starts

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

Feature Store And ML Data Pipelines

Overview

Use this skill when the platform must support model training and inference safely. It helps agents design feature generation, point-in-time correctness, serving parity, and operational contracts for ML-focused data products.

When to Use

  • building training datasets
  • designing feature stores or reusable features
  • supporting online and offline feature access
  • preventing leakage and training-serving mismatch
  • publishing model-ready data products

Do not treat feature pipelines as ordinary marts with different names. ML pipelines have different correctness risks.

Workflow

  1. Define the feature contract. Include:

    • entity key
    • feature meaning
    • update cadence
    • online or offline use
    • freshness expectation
  2. Protect point-in-time correctness. Training data must only include information available at prediction time.

  3. Align offline and online logic. Reuse definitions and validation wherever possible to prevent training-serving drift.

  4. Define feature lifecycle and ownership. Clarify:

    • producer
    • consumers
    • deprecation path
    • quality monitoring
  5. Validate operational behavior. Models break when stale or missing features silently propagate.

Common Rationalizations

Rationalization Reality
"We can use the latest value for training." That often introduces leakage and overstates model performance.
"Online parity is a model-team problem." Feature consistency is a data pipeline responsibility too.
"Features are internal, so contracts are unnecessary." Unclear feature meaning leads to misuse and drift.

Red Flags

  • no point-in-time logic is defined
  • offline and online definitions diverge
  • stale features are not monitored
  • feature ownership is unclear

Verification

  • Feature meaning, keys, and freshness are documented
  • Point-in-time correctness is protected
  • Offline and online parity expectations are explicit
  • Monitoring exists for stale, missing, or drifting features

Read the full file on GitHub · 69 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. 12d ago First seen · 69 lines · 49 tokens per session scan A b1c623fbd882

Subscribe to this mod's changes

feature-store-and-ml-data-pipelines is a skill published in the GitHub repository vaquarkhan/data-engineering-agent-skills (45 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 462 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.

Related

Other skills, from other repositories

kafka-shadowtraffic

Generate a ShadowTraffic configuration to populate a Kafka topic with realistic synthetic data. Discovers the target topic, its key and value schemas, and the correct serializers from the live cluster via any attached Kafka MCP server, then writes a ready-to-run shadowtraffic-config.json and Docker command. Use when…

lensesio/agentic-engineering-for-apache-kafka · 134 tokens

spark-training-gotchas

Preflight and diagnose the ten known failure modes for ML training on NVIDIA DGX Spark. Use when a training run on DGX Spark fails to start, OOMs below the 128GB limit, slows down mid-run, or before any multi-hour training job on GB10.

wshobson/agents · 63 tokens

9router

Entry point for 9Router — local/remote AI gateway with OpenAI-compatible REST for chat, image, TTS, embeddings, web search, web fetch. Use when the user mentions 9Router, NINEROUTERURL, or wants AI without writing provider boilerplate. This skill covers setup + indexes capability skills; fetch the relevant capability…

decolua/9router · 84 tokens

aeon

This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard…

synthetic-sciences/openscience · 74 tokens

lookml_ingest

Map a LookML view/model/explore into ktx semantic layer sources. Covers the LookML to ktx primitive table, provenance tagging, and three worked examples (overlay, standalone from derivedtable, standalone with sqlalwayswhere). Load when the turn contains .lkml content.

Kaelio/ktx · 63 tokens

markitdown

Convert files and office documents to Markdown. Supports PDF, DOCX, PPTX, XLSX, images (with OCR), audio (with transcription), HTML, CSV, JSON, XML, ZIP, YouTube URLs, EPubs and more.

synthetic-sciences/openscience · 53 tokens