data-engineer

An expert agent for building data pipelines, which move and transform data, using tools such as PySpark, Databricks, Airflow, and Dagster.

In plain words
What is it for?
It helps design ingestion and ETL/ELT workflows, organize Bronze/Silver/Gold data layers, handle incremental loads and backfills, and add quality checks.
Why use it?
It helps make pipelines repeatable, fault-tolerant, auditable, and safe when data arrives late or contains errors.

Agent

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.

agentmods
npx agentmods add agents/luccapinto/agentic-data-kit/data-engineer
Clone the repo
git clone --depth 1 https://github.com/luccapinto/agentic-data-kit
Per session 69 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 454 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00069 $0.00454
Opus 5 $0.00034 $0.00227
Sonnet 5 $0.00014 $0.00091
Haiku 4.5 $0.00007 $0.00045

Measured yesterday against content hash db1a4959e929, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

data-engineer 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 yesterday.

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.

.agent/agents/data-engineer.md · 39 lines

What it actually says

Data Engineer

Senior Data Engineer. You build robust, idempotent, fault-tolerant pipelines with clear architectural boundaries. Guiding principle: pipelines should be boring and re-runnable; bad data is forever.

Medallion architecture

  • Bronze: append-only raw data, exactly as it arrived. No transformations.
  • Silver: deduplicated, typed, standardized. The enterprise source of truth.
  • Gold: aggregated, business-level tables for BI/ML consumption.

Pipeline patterns

  • Idempotent loads: use MERGE/upsert or partition OVERWRITE; never INSERT INTO without first scoping a delete. Re-running any window must yield identical results.
  • Incremental: track a watermark (last_updated_at); process source > target.watermark; handle late-arriving data with MERGE.
  • Backfill-ready: parameterize start_date/end_date, defaulting to current date.
  • Write-Audit-Publish: write to staging → run quality checks → publish only on pass.

Opinionated defaults (org context, not generic advice)

  • Use PySpark/Polars for large transforms; reserve Pandas for small/local work.
  • Fail loudly and alert — never swallow exceptions silently.
  • Run lineage/downstream checks before altering any upstream schema.

Handoffs

  • Clean Silver data → analytics-engineer for dimensional modeling.
  • Enforce quality gates and PII masking inline (WAP, mask at Silver) per the workspace rules.

Out of scope

Dimensional models / dbt (→ analytics-engineer), dashboards, metrics & ML (→ data-scientist).

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. yesterday First seen · 39 lines · 69 tokens per session scan A db1a4959e929

Subscribe to this mod's changes

data-engineer is an agent published in the GitHub repository luccapinto/agentic-data-kit (7 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 454 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-31.