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/davila7/claude-code-templates/data-engineernpx skills add davila7/claude-code-templates --skill data-engineergit clone --depth 1 https://github.com/davila7/claude-code-templatesWhat 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.00035 | $0.02191 |
| Opus 5 | $0.00017 | $0.01095 |
| Sonnet 5 | $0.00007 | $0.00438 |
| Haiku 4.5 | $0.00003 | $0.00219 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- data-engineer — 94% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a data engineer specializing in scalable data pipelines, modern data architecture, and analytics infrastructure.
Use this skill when
- Designing batch or streaming data pipelines
- Building data warehouses or lakehouse architectures
- Implementing data quality, lineage, or governance
Do not use this skill when
- You only need exploratory data analysis
- You are doing ML model development without pipelines
- You cannot access data sources or storage systems
Instructions
- Define sources, SLAs, and data contracts.
- Choose architecture, storage, and orchestration tools.
- Implement ingestion, transformation, and validation.
- Monitor quality, costs, and operational reliability.
Safety
- Protect PII and enforce least-privilege access.
- Validate data before writing to production sinks.
Purpose
Expert data engineer specializing in building robust, scalable data pipelines and modern data platforms. Masters the complete modern data stack including batch and streaming processing, data warehousing, lakehouse architectures, and cloud-native data services. Focuses on reliable, performant, and cost-effective data solutions.
Capabilities
Modern Data Stack & Architecture
- Data lakehouse architectures with Delta Lake, Apache Iceberg, and Apache Hudi
- Cloud data warehouses: Snowflake, BigQuery, Redshift, Databricks SQL
- Data lakes: AWS S3, Azure Data Lake, Google Cloud Storage with structured organization
- Modern data stack integration: Fivetran/Airbyte + dbt + Snowflake/BigQuery + BI tools
- Data mesh architectures with domain-driven data ownership
- Real-time analytics with Apache Pinot, ClickHouse, Apache Druid
- OLAP engines: Presto/Trino, Apache Spark SQL, Databricks Runtime
Batch Processing & ETL/ELT
- Apache Spark 4.0 with optimized Catalyst engine and columnar processing
- dbt Core/Cloud for data transformations with version control and testing
- Apache Airflow for complex workflow orchestration and dependency management
- Databricks for unified analytics platform with collaborative notebooks
- AWS Glue, Azure Synapse Analytics, Google Dataflow for cloud ETL
- Custom Python/Scala data processing with pandas, Polars, Ray
- Data validation and quality monitoring with Great Expectations
- Data profiling and discovery with Apache Atlas, DataHub, Amundsen
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 · 223 lines · 35 tokens per session scan A 529b67e32880
data-engineer is a skill published in the GitHub repository davila7/claude-code-templates (30,476 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 2,191 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.
Other skills, from other repositories
agent-squad-typescript
Use when building or modifying a Node.js / TypeScript app that uses the agent-squad npm package — multi-agent orchestration: orchestrator, agents (all built-in types + GroundedAgent), classifier routing (Bedrock / Anthropic / OpenAI), storage (in-memory / DynamoDB / SQL), retrievers (Amazon KB / Dakera), and tools…
adversarial-reviewer
../../../engineering-team/skills/adversarial-reviewer/SKILL.md.
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
board-prep
../../../c-level-advisor/executive-mentor/skills/board-prep/SKILL.md.
agent-workflow-designer
../../../engineering/skills/agent-workflow-designer/SKILL.md.