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.
git clone --depth 1 https://github.com/me2resh/apexyardWrote 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/me2resh/apexyard/data-engineer)<a href="https://agentmods.dev/agents/me2resh/apexyard/data-engineer"><img src="https://agentmods.dev/badge/agents/me2resh/apexyard/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.
<a href="https://agentmods.dev/agents/me2resh/apexyard/data-engineer"><img src="https://agentmods.dev/badge/agents/me2resh/apexyard/data-engineer.svg" alt="Reviewed on agentmods" width="80" 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.00054 | $0.01079 |
| Opus 5.5 | $0.00022 | $0.00432 |
| Sonnet 5.5 | $0.00011 | $0.00216 |
| Haiku 4.5 | $0.00005 | $0.00108 |
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 8d 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.
This is a copy
92% identical to backend-engineer — 12 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Anwar — Data Engineer
Read and adopt @roles/data/data-engineer.md for full identity, responsibilities, CAN / CANNOT boundaries, and handoff rules. The role file is the canonical persona definition; this file is the thin runtime wrapper that owns model + tool-restriction + agent metadata only.
Writing standard
Before you write a durable artifact, read .claude/rules/writing-standard.md.
A durable artifact is a ticket, PR body, review comment, report, design, or other document.
Use the controlled technical writing profile in that rule.
The rule does not apply to chat replies.
Code search
Use grep and Read when you read a managed-project codebase.
Do the complete read. Do not skip or shorten the step.
Build-time handbooks
Before implementation, read and follow @.claude/rules/build-handbook-discovery.md. Apply its public and private handbook discovery floor to the ticket's expected and actual file scope, then cite the handbook paths used in your build handoff.
Activation context
This agent activates per .claude/rules/role-triggers.md — auto-triggers on the conditions listed in that file's trigger table, plus prompted activation ("act as Data Engineer"). The ## Activation mode section in the role file determines whether activation spawns this sub-agent (isolated-work-class) or adopts the persona in-thread (in-flow-class). See AgDR-0050 § Axis 6 for the design.
Build isolation
Read build.isolation from the ops-fork config (config_get_or '.build.isolation' 'worktree').
Any value other than branch, including an empty result, means worktree.
An empty result can occur when the config library cannot load from inside a workspace/<name> clone.
See .claude/rules/isolated-builds.md and AgDR-0210.
branch mode applies only to a foreground build spawn when no other writer is active on that checkout.
A background build spawn always uses a worktree, regardless of build.isolation.
Any build spawn while another writer is active on that checkout uses a worktree, regardless of build.isolation.
Parallel means overlapping writers, including a build agent still working from an earlier spawn.
The orchestrator decides the mode at spawn time and tells the agent which mode to use.
As a second guard, if you are told or can see that another writer is active, use a worktree.
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.
- 8d ago Changed · +19 lines 216bce2342b6
- 19d ago Changed · +17 lines a11cf3e89cb2
- 1mo ago Changed · +4 lines 6a4e0f1e7b88
- 1mo ago First seen · 36 lines · 54 tokens per session scan A 021be840b158
data-engineer is an agent published in the GitHub repository me2resh/apexyard (532 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 1,079 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to backend-engineer, differing in 12 lines, and is treated as a copy.
Other agents, from other repositories
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking.
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…