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/chandrudp29/skillhub/data-pipelinenpx skills add chandrudp29/skillhub --skill data-pipelinegit clone --depth 1 https://github.com/chandrudp29/skillhubWrote 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/chandrudp29/skillhub/data-pipeline)<a href="https://agentmods.dev/skills/chandrudp29/skillhub/data-pipeline"><img src="https://agentmods.dev/badge/skills/chandrudp29/skillhub/data-pipeline.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.1 | $0.00035 | $0.01113 |
| Opus 5 | $0.00017 | $0.00557 |
| Sonnet 5 | $0.00007 | $0.00223 |
| Haiku 4.5 | $0.00003 | $0.00111 |
Grade A, and why
data-pipeline 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 5d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Apply when building, reviewing, or debugging data pipelines, ETL jobs, or data orchestration workflows.
Core Rules
- All pipelines must be idempotent — running twice gives the same result as running once
- Prefer ELT over ETL — load raw first, transform in the warehouse (cheaper to re-transform than re-extract)
- Always use incremental loads over full loads for tables > 100K rows
- Fail fast and loudly — a silent partial load is worse than a visible failure
- Test transformations with fixed fixtures, not prod data samples
Idempotency Patterns
# ❌ Non-idempotent — double run = double rows
def load_events(conn, events):
for event in events:
conn.execute("INSERT INTO events VALUES (?)", event)
# ✓ Idempotent — delete-then-insert by partition
def load_events(conn, events, date: str):
conn.execute("DELETE FROM events WHERE date = ?", date)
conn.executemany("INSERT INTO events VALUES (?)", events)
# ✓ UPSERT — idempotent by natural key
def upsert_users(conn, users):
conn.executemany("""
INSERT INTO users (id, email, name, updated_at)
VALUES (?, ?, ?, ?)
ON CONFLICT (id) DO UPDATE SET
email = excluded.email,
name = excluded.name,
updated_at = excluded.updated_at
""", users)
Incremental Load Pattern
from datetime import datetime, timedelta
def get_last_watermark(conn, table: str) -> datetime:
row = conn.execute(
"SELECT MAX(watermark) FROM pipeline_state WHERE table_name = ?", table
).fetchone()
return row[0] or datetime(2020, 1, 1)
def update_watermark(conn, table: str, watermark: datetime):
conn.execute("""
INSERT INTO pipeline_state (table_name, watermark)
VALUES (?, ?)
ON CONFLICT (table_name) DO UPDATE SET watermark = excluded.watermark
""", (table, watermark))
def load_incremental(source_conn, dest_conn, table: str):
last = get_last_watermark(dest_conn, table)
new_watermark = datetime.utcnow()
rows = source_conn.execute(
f"SELECT * FROM {table} WHERE updated_at > ?", last
).fetchall()
upsert_rows(dest_conn, table, rows)
update_watermark(dest_conn, table, new_watermark)
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.
- 5d ago First seen · 140 lines · 35 tokens per session scan A 7312416e9d84
data-pipeline is a skill published in the GitHub repository chandrudp29/skillhub (13 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,113 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.
Other skills, from other repositories
Data Pipeline Architect
Design and implement robust data pipelines — ETL/ELT, streaming, batch processing. From architecture to code with Airflow, dbt, Kafka, and modern data stack.
data-engineer
Builds data infrastructure — ETL/ELT pipelines, data warehousing, stream processing, data quality, orchestration (Airflow/Dagster), and analytics engineering (dbt). Use when the user asks to build data pipelines, set up ETL/ELT workflows, design a data warehouse, configure stream processing, or implement analytics…
airflow
Apache Airflow workflow orchestration reference. Covers DAG authoring (TaskFlow API + classic), operators, sensors, connections, XComs, deployment (Docker, Kubernetes, Helm), testing, and common patterns including dynamic task mapping and data-aware scheduling.
airflow-hitl
Builds human-in-the-loop (HITL) Airflow workflows - approval gates, form input, and human-driven branching. Use when a DAG needs a human in the loop - an approval or reject step, sign-off before a task runs, a decision or approval UI, branching on a human choice, or collecting form input mid-run; also on mentions of…
airflow-plugins
Builds Airflow 3.1+ plugins that embed FastAPI apps, custom UI pages, React components, middleware, macros, and operator links directly into the Airflow UI. Use when building anything custom inside Airflow 3.1+ that involves Python and a browser-facing interface - creating an Airflow plugin, adding a custom UI page or…
airflow-state-store
Persists task and asset state across retries and DAG runs using Airflow 3.3's AIP-103 key/value stores (taskstatestore, assetstatestore) and the crash-safe ResumableJobMixin. Use when the user asks about task state store, checkpointing in tasks, persisting state across retries, job IDs surviving worker crashes…