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/kid-sid/codex-spellbook/data-pipelinesnpx skills add kid-sid/codex-spellbook --skill data-pipelinesgit clone --depth 1 https://github.com/kid-sid/codex-spellbookWrote 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/kid-sid/codex-spellbook/data-pipelines)<a href="https://agentmods.dev/skills/kid-sid/codex-spellbook/data-pipelines"><img src="https://agentmods.dev/badge/skills/kid-sid/codex-spellbook/data-pipelines.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.00052 | $0.04241 |
| Opus 5 | $0.00026 | $0.02121 |
| Sonnet 5 | $0.00010 | $0.00848 |
| Haiku 4.5 | $0.00005 | $0.00424 |
Grade A, and why
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 3d 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 — 525 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Pipelines
Orchestration, transformation, and validation patterns for production data pipelines.
When to Activate
- Writing Airflow DAGs, operators, sensors, or XComs
- Building dbt models, sources, tests, or macros
- Designing incremental vs full-load strategies
- Implementing idempotent pipeline runs
- Validating data quality with dbt tests or Great Expectations
- Orchestrating multi-step ELT/ETL workflows
- Debugging failed runs, backfills, or data freshness issues
ETL vs ELT Decision
| Approach | Transform where | Use when |
|---|---|---|
| ETL | Before loading (in pipeline code) | Target warehouse has limited compute; PII must be masked before storage |
| ELT | After loading (in warehouse SQL) | Modern warehouse (BigQuery, Snowflake, Redshift); raw data must be preserved |
| Streaming | Continuously (Kafka + Flink/Spark) | Sub-minute latency required; event sourcing |
Default for modern stacks: ELT — land raw data, transform with dbt, version-control SQL.
Airflow
DAG Structure
from datetime import datetime, timedelta
from airflow.decorators import dag, task
from airflow.operators.python import PythonOperator
from airflow.providers.postgres.hooks.postgres import PostgresHook
@dag(
schedule="0 6 * * *", # 6 AM daily
start_date=datetime(2026, 1, 1),
catchup=False, # don't backfill missed runs on deploy
max_active_runs=1, # prevent overlapping runs
default_args={
"retries": 3,
"retry_delay": timedelta(minutes=5),
"retry_exponential_backoff": True,
"email_on_failure": True,
},
tags=["finance", "daily"],
)
def daily_revenue_pipeline():
@task
def extract_orders(execution_date=None) -> list[dict]:
hook = PostgresHook(postgres_conn_id="source_db")
# Use execution_date for idempotent extraction
rows = hook.get_records(
"SELECT * FROM orders WHERE date = %s",
parameters=[execution_date.date()],
)
return [dict(r) for r in rows]
@task
def transform(orders: list[dict]) -> list[dict]:
return [
{**o, "revenue_usd": o["amount"] * o["fx_rate"]}
for o in orders
if o["status"] == "completed"
]
@task
def load(records: list[dict], execution_date=None):
hook = PostgresHook(postgres_conn_id="warehouse")
# Idempotent: delete-then-insert for the partition date
hook.run("DELETE FROM daily_revenue WHERE date = %s", parameters=[execution_date.date()])
hook.insert_rows("daily_revenue", [[r["date"], r["revenue_usd"]] for r in records])
orders = extract_orders()
transformed = transform(orders)
load(transformed)
dag = daily_revenue_pipeline()
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.
- 3d ago First seen · 525 lines · 52 tokens per session scan A b63132d946e8
data-pipelines is a skill published in the GitHub repository kid-sid/codex-spellbook (21 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 4,241 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…