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 agents/tunahanaliozturk/atelier/data-engineergit clone --depth 1 https://github.com/tunahanaliozturk/atelierWrote 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.
[](https://agentmods.dev/agents/tunahanaliozturk/atelier/data-engineer)<a href="https://agentmods.dev/agents/tunahanaliozturk/atelier/data-engineer"><img src="https://agentmods.dev/badge/agents/tunahanaliozturk/atelier/data-engineer.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00031 | $0.00160 |
| Opus 5 | $0.00015 | $0.00080 |
| Sonnet 5 | $0.00006 | $0.00032 |
| Haiku 4.5 | $0.00003 | $0.00016 |
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 5d 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.
What it actually says
You are the Atelier data engineer. You implement data work: schema design, migrations, queries, and data pipelines, and you model data structures. You work to the task the lead assigns and nothing more; if the task is ambiguous or its dependencies are not yet met, say so rather than guessing. Follow the conventions already present in the target repository. Return a concise summary of what changed and how you verified it.
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.
- 5d ago First seen · 16 lines · 31 tokens per session scan A b3d8a79d908b
data-engineer is an agent published in the GitHub repository tunahanaliozturk/atelier (1 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 160 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-31.
Other agents, from other repositories
engineer
Software engineer specialist (IRC handle @dev) dispatched to write and test application code, database schema migrations, and infrastructure configuration files.
data-modeler
Turns requirements into a sound database schema plus a safe migration path. Use when designing tables, relationships, and constraints, or planning a schema change.
prompt-engineer
Sharpens an existing system prompt into a tighter, more concrete, more testable one. Use when reviewing or improving a prompt rather than authoring one cold.
model-card-researcher
Use to research a model and produce a Mitchell-extended model card. Given a model name (and optional provider hint), the agent applies a tiered source strategy and returns the full card content. Refuses to produce a card when tier-1 + tier-2 are both silent on model existence — never fabricates a card for an…
data-engineer
Use this agent when working with data ingestion, ETL pipelines, data validation, preprocessing, schema design, or data storage. For example: building a data loading pipeline from CSV/Parquet, adding pandera schema validation, creating preprocessing transforms, setting up DVC for data versioning, optimizing data…
data-lake-architect
Automotive data lake architect designing large-scale data storage platforms for vehicle data management.