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/bybren-llc/safe-agentic-workflowWrote 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/safe-agentic-workflow/data-engineer)<a href="https://agentmods.dev/agents/bybren-llc/safe-agentic-workflow/data-engineer"><img src="https://agentmods.dev/badge/agents/bybren-llc/safe-agentic-workflow/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/bybren-llc/safe-agentic-workflow/data-engineer"><img src="https://agentmods.dev/badge/agents/bybren-llc/safe-agentic-workflow/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.00012 | $0.02346 |
| Opus 5.5 | $0.00005 | $0.00938 |
| Sonnet 5.5 | $0.00002 | $0.00469 |
| Haiku 4.5 | $0.00001 | $0.00235 |
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 1mo 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
2 near-identical copies found in the catalogue:
- data-engineer — 92% identical, 50 lines differ
- data-engineer — 91% identical, 28 lines differ
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 [{{TICKET_PREFIX}}-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 ({{TICKET_PREFIX}}-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 @{{AUTHOR_HANDLE}} 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.
- 1mo ago First seen · 326 lines · 12 tokens per session scan A 0c40e108b255
data-engineer is an agent published in the GitHub repository bybren-llc/safe-agentic-workflow (423 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 2,346 once invoked, about $0.0000 per session on Opus 5.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 agents, from other repositories
directus-developer
Build and customize Directus applications with extensions, hooks, and API integrations. Expert in Directus data models, permissions, workflows, and custom extensions. Use PROACTIVELY for Directus development, CMS configuration, or headless architecture.
data-scientist
Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.
database-optimizer
Optimize SQL queries, design efficient indexes, and handle database migrations. Solves N+1 problems, slow queries, and implements caching. Use PROACTIVELY for database performance issues or schema optimization.
backend-architect
Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.
database-admin
Manage database operations, backups, replication, and monitoring. Handles user permissions, maintenance tasks, and disaster recovery. Use PROACTIVELY for database setup, operational issues, or recovery procedures.
database-optimization
Database performance specialist focusing on query optimization, indexing strategies, schema design, connection pooling, and database monitoring. Covers SQL optimization, NoSQL tuning, and architecture best practices.