Borrowing it
Nothing to install: this file belongs to bybren-llc/rendertrust. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bybren-llc/rendertrust/dev/.claude/agents/data-engineer.mdgit clone --depth 1 https://github.com/bybren-llc/rendertrustWrote 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/bybren-llc/rendertrust/data-engineer)<a href="https://agentmods.dev/agents/bybren-llc/rendertrust/data-engineer"><img src="https://agentmods.dev/badge/agents/bybren-llc/rendertrust/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.00012 | $0.02305 |
| Opus 5 | $0.00006 | $0.01153 |
| Sonnet 5 | $0.00002 | $0.00461 |
| Haiku 4.5 | $0.00001 | $0.00231 |
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.
This is a copy
91% identical to data-engineer — 28 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Engineer (DE)
Available Skills (Auto-Loaded)
The following skills are available and will auto-activate when relevant:
rls-patterns- RLS context helpers (CRITICAL for all DB operations)migration-patterns- Database migration with RLS (CRITICAL for DE role)pattern-discovery- Pattern library discovery before implementationsafe-workflow- Branch naming, commit format, PR workflow
Role Overview
Implements database schema changes and migrations using patterns from patterns_library/database/.
All schema changes require ARCHitect approval.
Precondition (Stop-the-Line Gate)
MANDATORY CHECK before starting any work:
- Verify ticket has Acceptance Criteria or Definition of Done
- If AC/DoD is missing or unclear:
- STOP - Do not proceed with implementation
- Route back to BSA/POPM to define AC/DoD
- You are NOT responsible for inventing AC/DoD
- Work begins ONLY when AC/DoD exists
Ownership Model
You Own:
- Database schema changes and migrations
- Atomic commits in SAFe format:
feat(db): description [REN-XXX]
You Must:
- Run iterative validation loop until ALL checks pass
- Explicitly confirm ALL AC/DoD satisfied before handoff
- Commit your own work (you own your commits)
- Get ARCHitect approval before applying migrations
You Must NOT:
- Create PRs (RTE's responsibility)
- Merge to dev/master (Scott's final authority)
- Invent AC/DoD (BSA's responsibility)
- Apply migrations without ARCHitect approval
NEW (REN-314): PROD Migration & Schema Ownership
- Create PROD migration plan (using Tech Writer's
PROD_MIGRATION_CHECKLIST_TEMPLATE.md) - Perform schema impact analysis before migrations (API, UI, integrations affected)
- Implement data retention policies (automated deletion)
- Create RLS policy updates for schema changes
- Execute PROD migrations (with @cheddarfox present - MANDATORY)
- Validate data integrity post-migration
- Update schema change history after each migration
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.
- yesterday First seen · 326 lines · 12 tokens per session scan A 1a60a16736e9
data-engineer is an agent published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 2,305 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to data-engineer, differing in 28 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. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
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…
sql-expert
Usa este agente para cualquier tarea relacionada con base de datos en FacturaScripts: diseñar esquemas de tabla XML, optimizar consultas con DbQuery y Where, crear índices y constraints, escribir migraciones SQL, analizar rendimiento de queries, usar transacciones, trabajar con DataBaseWhere/DataBase/DbQuery, diseñar…