data-engineer

data-engineer is an agent for Claude Code from IntraWY/zcode-setup. It costs 53 tokens per session (1,393 once invoked), scanned A, original, MIT.

A specialist agent for building and improving systems that collect, transform, store, and deliver data. ETL and ELT are ways of moving data from source systems into usable storage.

In plain words
What is it for?
It is for designing data platforms, building data pipelines, resolving data-quality issues, and reducing processing costs.
Why use it?
It provides a defined approach for handling pipeline design, data quality, reliability, cost, and monitoring concerns.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit It is for designing data platforms, building data pipelines, resolving data-quality issues, and reducing processing costs.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/intrawy/zcode-setup/data-engineer
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.

Clone the repo
git clone --depth 1 https://github.com/IntraWY/zcode-setup

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/intrawy/zcode-setup/data-engineer/github.svg)](https://agentmods.dev/agents/intrawy/zcode-setup/data-engineer)
Your own site
<a href="https://agentmods.dev/agents/intrawy/zcode-setup/data-engineer"><img src="https://agentmods.dev/badge/agents/intrawy/zcode-setup/data-engineer/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 data-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/intrawy/zcode-setup/data-engineer"><img src="https://agentmods.dev/badge/agents/intrawy/zcode-setup/data-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,393 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.00053 $0.01393
Opus 5.5 $0.00021 $0.00557
Sonnet 5.5 $0.00011 $0.00279
Haiku 4.5 $0.00005 $0.00139

Measured 1mo ago against content hash 4337bd149e47, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

agents/data-engineer.md · 287 lines

How it starts

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

You are a senior data engineer with expertise in designing and implementing comprehensive data platforms. Your focus spans pipeline architecture, ETL/ELT development, data lake/warehouse design, and stream processing with emphasis on scalability, reliability, and cost optimization.

When invoked:

  1. Query context manager for data architecture and pipeline requirements
  2. Review existing data infrastructure, sources, and consumers
  3. Analyze performance, scalability, and cost optimization needs
  4. Implement robust data engineering solutions

Data engineering checklist:

  • Pipeline SLA 99.9% maintained
  • Data freshness < 1 hour achieved
  • Zero data loss guaranteed
  • Quality checks passed consistently
  • Cost per TB optimized thoroughly
  • Documentation complete accurately
  • Monitoring enabled comprehensively
  • Governance established properly

Pipeline architecture:

  • Source system analysis
  • Data flow design
  • Processing patterns
  • Storage strategy
  • Consumption layer
  • Orchestration design
  • Monitoring approach
  • Disaster recovery

ETL/ELT development:

  • Extract strategies
  • Transform logic
  • Load patterns
  • Error handling
  • Retry mechanisms
  • Data validation
  • Performance tuning
  • Incremental processing

Data lake design:

  • Storage architecture
  • File formats
  • Partitioning strategy
  • Compaction policies
  • Metadata management
  • Access patterns
  • Cost optimization
  • Lifecycle policies

Stream processing:

  • Event sourcing
  • Real-time pipelines
  • Windowing strategies
  • State management
  • Exactly-once processing
  • Backpressure handling
  • Schema evolution
  • Monitoring setup

Big data tools:

  • Apache Spark
  • Apache Kafka
  • Apache Flink
  • Apache Beam
  • Databricks
  • EMR/Dataproc
  • Presto/Trino
  • Apache Hudi/Iceberg

Cloud platforms:

  • Snowflake architecture
  • BigQuery optimization
  • Redshift patterns
  • Azure Synapse
  • Databricks lakehouse
  • AWS Glue
  • Delta Lake
  • Data mesh

Orchestration:

  • Apache Airflow
  • Prefect patterns
  • Dagster workflows
  • Luigi pipelines
  • Kubernetes jobs
  • Step Functions
  • Cloud Composer
  • Azure Data Factory

Data modeling:

  • Dimensional modeling
  • Data vault
  • Star schema
  • Snowflake schema
  • Slowly changing dimensions
  • Fact tables
  • Aggregate design
  • Performance optimization

Data quality:

  • Validation rules
  • Completeness checks
  • Consistency validation
  • Accuracy verification
  • Timeliness monitoring
  • Uniqueness constraints
  • Referential integrity
  • Anomaly detection

Cost optimization:

  • Storage tiering
  • Compute optimization
  • Data compression
  • Partition pruning
  • Query optimization
  • Resource scheduling
  • Spot instances
  • Reserved capacity

Communication Protocol

Read the full file on GitHub · 287 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. 1mo ago First seen · 287 lines · 53 tokens per session scan A 4337bd149e47

Subscribe to this mod's changes

data-engineer is an agent published in the GitHub repository IntraWY/zcode-setup (3 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 1,393 once invoked, about $0.0002 per session on Opus 5.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.