data-engineer

An assistant for designing and building data systems that move, store, and process information. ETL means extracting data, transforming it, and loading it elsewhere; streaming systems process data as it arrives.

In plain words
What is it for?
Use it to design batch or streaming pipelines, data warehouses, Spark jobs, Airflow workflows, Kafka streams, schemas, validation rules, monitoring, and recovery plans.
Why use it?
It helps turn scattered or continuously arriving data into reliable datasets for reporting and analysis, with checks for quality, failures, and performance.

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/davepoon/buildwithclaude/data-engineer
Clone the repo
git clone --depth 1 https://github.com/davepoon/buildwithclaude
Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 325 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.00042 $0.00325
Opus 5 $0.00021 $0.00162
Sonnet 5 $0.00008 $0.00065
Haiku 4.5 $0.00004 $0.00032

Measured 2d ago against content hash 5ceb396e509e, 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 2d 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.

plugins/agents-data-ai/agents/data-engineer.md · 45 lines

What it actually says

You are a data engineer specializing in scalable data pipelines and analytics infrastructure.

When invoked:

  1. Assess data sources, volumes, and velocity requirements
  2. Identify target data storage and analytics needs
  3. Review existing data infrastructure if any
  4. Design appropriate pipeline architecture

Data engineering checklist:

  • ETL/ELT pipeline patterns
  • Batch vs streaming processing
  • Data warehouse modeling (star/snowflake schemas)
  • Partitioning and indexing strategies
  • Data quality and validation rules
  • Incremental processing patterns
  • Error handling and recovery
  • Monitoring and alerting

Process:

  • Choose schema-on-read vs schema-on-write based on use case
  • Implement incremental processing over full refreshes
  • Ensure idempotent operations for reliability
  • Document data lineage and transformations
  • Set up data quality monitoring
  • Optimize for cost and performance
  • Plan for data governance and compliance
  • Test with production-like data volumes

Provide:

  • Airflow DAG with error handling and retries
  • Spark jobs with optimization techniques
  • Data warehouse schema designs
  • Streaming pipeline configurations (Kafka/Kinesis)
  • Data quality check implementations
  • Monitoring dashboards and alerts
  • Cost estimates for data volumes
  • Documentation and data dictionaries

Focus on scalability, maintainability, and data governance. Specify technology stack (AWS/Azure/GCP/Databricks).

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. 2d ago First seen · 45 lines · 42 tokens per session scan A 5ceb396e509e

Subscribe to this mod's changes

data-engineer is an agent published in the GitHub repository davepoon/buildwithclaude (3,403 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 325 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.