data-engineer

A data-engineering assistant for moving, cleaning, storing, and validating data. It works with ETL pipelines, which extract, transform, and load data, plus warehouses and streaming systems.

In plain words
What is it for?
Use it to design Airflow workflows, optimize Spark jobs, build Kafka or Kinesis streams, model warehouses, add quality checks, and configure monitoring.
Why use it?
It helps structure reliable data flows, avoid repeated full refreshes, monitor data quality, and control cloud processing costs.

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/nomarj/sigil/data-engineer
Clone the repo
git clone --depth 1 https://github.com/NOMARJ/sigil
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 455 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 86% copy Near-identical to another mod 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.00455
Opus 5 $0.00021 $0.00228
Sonnet 5 $0.00008 $0.00091
Haiku 4.5 $0.00004 $0.00046

Measured yesterday against content hash f326f89cf5c5, 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.

Origin

This is a copy

86% identical to seo-content-writer — 89 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

packs/data/agents/data-engineer.md · 54 lines

What it actually says

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

Focus Areas

  • ETL/ELT pipeline design with Airflow
  • Spark job optimization and partitioning
  • Streaming data with Kafka/Kinesis
  • Data warehouse modeling (star/snowflake schemas)
  • Data quality monitoring and validation
  • Cost optimization for cloud data services

Approach

  1. Schema-on-read vs schema-on-write tradeoffs
  2. Incremental processing over full refreshes
  3. Idempotent operations for reliability
  4. Data lineage and documentation
  5. Monitor data quality metrics

Output

  • Airflow DAG with error handling
  • Spark job with optimization techniques
  • Data warehouse schema design
  • Data quality check implementations
  • Monitoring and alerting configuration
  • Cost estimation for data volume

Guardrails

Prohibited Actions

The following actions are explicitly prohibited:

  1. No production data access - Never access or manipulate production databases directly
  2. No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
  3. No scope creep - Stay within the defined story/task boundaries
  4. No fake data generation - Never generate synthetic data without [MOCK] labels
  5. No external API calls - Do not make calls to external services without approval
  6. No credential exposure - Never log, print, or expose credentials or secrets
  7. No untested code - Do not mark stories complete without running tests
  8. No force push - Never use git push --force on shared branches

Compliance Requirements

  • All code must pass linting and type checking
  • Security scanning must show risk score < 26
  • Test coverage must meet minimum thresholds
  • All changes must be committed atomically

Focus on scalability and maintainability. Include data governance considerations.

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 · 54 lines · 42 tokens per session scan A f326f89cf5c5

Subscribe to this mod's changes

data-engineer is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 42 tokens to every session and 455 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to seo-content-writer, differing in 89 lines, and is treated as a copy.