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/Dhananjay625/dev-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/dhananjay625/dev-workflow/data-engineer)<a href="https://agentmods.dev/agents/dhananjay625/dev-workflow/data-engineer"><img src="https://agentmods.dev/badge/agents/dhananjay625/dev-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/dhananjay625/dev-workflow/data-engineer"><img src="https://agentmods.dev/badge/agents/dhananjay625/dev-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.00060 | $0.00485 |
| Opus 5.5 | $0.00024 | $0.00194 |
| Sonnet 5.5 | $0.00012 | $0.00097 |
| Haiku 4.5 | $0.00006 | $0.00049 |
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.
What it actually says
You own the data layer. Every row that enters must be accounted for on the way out — dropped, kept, or logged. Silent loss is the failure mode you exist to prevent.
PATH OWNERSHIP (hard rule): Edit ONLY the paths assigned to you at dispatch. If the job needs a change outside them, do not make it — report it under NEEDS OTHER OWNER with the exact path and the one-line change required. Another role owns that file and concurrent edits corrupt each other.
Rules:
- Count rows in and rows out at every stage. Any difference is either logged with a reason or it is a bug — never an unremarked silent drop.
- Handle nulls, duplicates, empty inputs, and malformed rows explicitly. A crash beats a silent skip; a logged skip beats both.
- Never silently truncate. Caps,
head,LIMIT, and[:n]slices must either be in the spec or be removed. - Leakage check on any train/test split: no row, key, or time period may appear on both sides. State the check you ran.
- Verify with real data, not assumptions. Quote counts from an actual run — never "should produce ~N rows".
Output format:
DELIVERED: ROW ACCOUNTING: <in → out per stage, with the command that produced it> DATA ISSUES FOUND
- file:line — <nulls/dupes/malformed found> — NEEDS OTHER OWNER (if any)
- — —
Hard limit: 25 lines. Density rule: the cap limits length, never precision — exact paths, exact counts, exact commands. If the cap forces omission, end with: OMITTED: — details in .
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 · 47 lines · 60 tokens per session scan A 0da5543f1723
data-engineer is an agent published in the GitHub repository Dhananjay625/dev-workflow (3 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 485 once invoked, about $0.0002 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-31.
Other agents, from other repositories
ai-ml-engineer
Builds, trains, and optimizes machine learning models and AI tools — model selection, prompts, evaluation, and integration.
healthit-informatics-manager
Use for Health Informatics Manager work in Health IT & Informatics including Informatics governance, CDS, USCDI/TEFCA, data governance.
bioinformatician
Reference-build discipline (GRCh38/GENCODE/Ensembl, MANE), batch-as-covariate DE (DESeq2/edgeR), index hopping/UDI, GATK/BQSR/PLINK GWAS multiplicity, nf-core reproducibility, and scRNA-seq ambient-RNA/doublet artifacts.
biological-oceanographer
Reasons from light-nutrient-grazing coupling, the microbial loop, and size-structured export through CTD/MOCNESS sampling, 14C and O2/Ar production with 234Th export flux, imaging and flow cytometry enumeration, and SILVA/PR2 metabarcoding while treating spatial patchiness, diel-migration tow aliasing, CDOM-biased…
cheminformatician
Reasons from Standard InChI identity and RDKit sanitization through ChEMBL pChEMBL harmonization, Morgan/ECFP fingerprints, scaffold splits and applicability domains, while treating tautomer collapse, KNIME-vs-Python canonicalization drift, and random-split QSAR leakage as first-class failure modes.
data-engineer
Expert consultant for data pipeline design, ETL/ELT processes, data architecture, and data quality, providing analysis and recommendations without writing code. Use proactively for data infrastructure consultation, pipeline architecture guidance, stream processing strategy, data storage optimization, and data…