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/nonlinear-xyz/factory-kit/data-pipeline-engineergit clone --depth 1 https://github.com/nonlinear-xyz/factory-kitWrote 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/nonlinear-xyz/factory-kit/data-pipeline-engineer)<a href="https://agentmods.dev/agents/nonlinear-xyz/factory-kit/data-pipeline-engineer"><img src="https://agentmods.dev/badge/agents/nonlinear-xyz/factory-kit/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.00102 | $0.00172 |
| Opus 5 | $0.00051 | $0.00086 |
| Sonnet 5 | $0.00020 | $0.00034 |
| Haiku 4.5 | $0.00010 | $0.00017 |
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 4d 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
Apply the preloaded factory-data-pipeline-engineer skill to the delegated task. The canonical skill is the complete workflow and source of truth.
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.
- 4d ago First seen · 11 lines · 102 tokens per session scan A d144a05985a1
data-pipeline-engineer is an agent published in the GitHub repository nonlinear-xyz/factory-kit (9 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 172 once invoked, about $0.0005 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-31.
Other agents, from other repositories
experience-extractor
Learning agent for the Self-Evolving Loop. Use when executing /evolving-loop Phase LEARN — after completion-judge decides EVOLVE, when iterations fail with similar issues, before the evolve phase, or on SHIP to record success patterns. Runs evidence-based root-cause analysis, extracts patterns, writes learning.json…
agents-expert
Expert on creating and configuring custom Claude Code agents (subagents). Use PROACTIVELY when the user mentions creating an agent, custom agent, or subagent; when designing specialized agents for project tasks; when troubleshooting agent invocation, tools, or model config; or during /agents-generate. Knows the…
hooks-expert
Expert on Claude Code hooks — event-driven automation for tool calls, prompts, sessions, and notifications. Use PROACTIVELY when the user mentions "hook", "automation", or "trigger"; when designing PreToolUse/PostToolUse/Stop/UserPromptSubmit hooks or security guards; or during hook setup. Knows the hook event list…
requirement-analyzer
Deep requirement analysis agent for the Self-Evolving Loop. Use when executing /evolving-loop Phase ANALYZE — starting a new loop session, when the user provides a new requirement or feature request, or when re-analyzing after a failed iteration. Extracts acceptance criteria, a complexity score, an implementation…
doc-writer
Documentation specialist for README, API docs, code comments, and technical writing. Use when creating or updating documentation, after new features, or when docs drift from code. Verifies examples against the actual codebase before writing. user: "I added a new /export endpoint but the API docs don't mention it yet."…
knowledge-gardener
Surveys the graph and notes what has gone leggy or stale — never prunes. Use this agent for read-only knowledge graph auditing: inventory, schema validation, orphan detection, relation integrity, staleness, version drift, tag alignment, and note-quality checks. Typical triggers include: "audit my knowledge graph"…