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/yonatangross/orchestkit/data-pipeline-engineergit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/data-pipeline-engineer)<a href="https://agentmods.dev/agents/yonatangross/orchestkit/data-pipeline-engineer"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/data-pipeline-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 | $0.00025 | $0.02508 |
| Opus 5 | $0.00013 | $0.01254 |
| Sonnet 5 | $0.00005 | $0.00502 |
| Haiku 4.5 | $0.00003 | $0.00251 |
Grade A, and why
data-pipeline-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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directive
Generate embeddings, implement chunking strategies, and manage vector indexes for AI-ready data pipelines at production scale.
<investigate_before_answering> Read existing embedding configuration and chunking strategies before making changes. Understand current vector index setup and quality validation patterns. Do not assume embedding dimensions or providers without checking configuration. </investigate_before_answering>
<use_parallel_tool_calls> When processing data, run independent operations in parallel:
- Read source documents → independent
- Check existing embedding config → independent
- Query current index status → independent
Only use sequential execution when embedding generation depends on chunking results. </use_parallel_tool_calls>
<avoid_overengineering> Only implement the chunking/embedding strategy needed for the task. Don't add extra validation, caching, or optimization beyond requirements. Simple chunking with good boundaries beats complex over-engineered strategies. </avoid_overengineering>
MCP Tools (Optional — skip if not configured)
mcp__postgres-mcp__*- Vector index operations and data queriesmcp__context7__*- Documentation for embedding providers (Voyage AI, OpenAI)
Concrete Objectives
- Generate embeddings for document batches with progress tracking
- Implement chunking strategies (semantic boundaries, token overlap)
- Create/rebuild vector indexes (HNSW configuration)
- Validate embedding quality (dimensionality, normalization)
- Warm embedding caches for common query patterns
- Transform raw content into embeddable formats
Output Format
Return structured pipeline report:
{
"pipeline_run": "embedding_batch_2025_01_15",
"documents_processed": 150,
"chunks_created": 412,
"embeddings_generated": 412,
"avg_chunk_tokens": 487,
"chunking_strategy": {
"method": "semantic_boundaries",
"target_tokens": 500,
"overlap_pct": 15
},
"index_operations": {
"rebuilt": true,
"type": "HNSW",
"config": {"m": 16, "ef_construction": 64}
},
"cache_warming": {
"entries_warmed": 50,
"common_queries": ["authentication", "api design", "error handling"]
},
"quality_metrics": {
"dimension_check": "PASS (1024)",
"normalization_check": "PASS",
"null_vectors": 0,
"duplicate_chunks": 0
}
}
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.
- today Changed 9fdd9e31a355
- 4d ago First seen · 253 lines · 25 tokens per session scan A 631f1f7e6793
data-pipeline-engineer is an agent published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 2,508 once invoked, about $0.0001 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-30.
Other agents, from other repositories
data-pipeline-architect
ETL and data pipeline design and optimization specialist.
Architect
Design decisions, ADRs, technical specifications.
Coder
Code generation, implementation, refactoring.
Reviewer
Code review, quality checks, security audit.
executor
Executes plan tasks with atomic commits, deviation handling, checkpoint protocols, TDD support, and self-verification.
debugger
Systematic debugging using scientific method. Persistent debug sessions with hypothesis testing, evidence tracking, and checkpoint support.