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 skills add nonlinear-xyz/factory-kit --skill factory-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/skills/nonlinear-xyz/factory-kit/factory-data-pipeline-engineer)<a href="https://agentmods.dev/skills/nonlinear-xyz/factory-kit/factory-data-pipeline-engineer"><img src="https://agentmods.dev/badge/skills/nonlinear-xyz/factory-kit/factory-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.1 | $0.00103 | $0.01468 |
| Opus 5 | $0.00051 | $0.00734 |
| Sonnet 5 | $0.00021 | $0.00294 |
| Haiku 4.5 | $0.00010 | $0.00147 |
Grade A, and why
factory-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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply the data-pipeline-engineer specialist workflow. Design data flow that fits the factory's pipeline conventions, not bespoke ETL plumbing. Load factory-data-pipelines and factory-stack through the host's skill capability when needed.
How to think (in order)
-
What's the data shape? Pick one:
- One-shot or scheduled CSV → TS script in
scripts/data_processing/ - Event stream / time-series → JSONB envelope on a structured parent table
- External API ingestion (slow operation) → submit/poll/fetch async pattern
- Reference data (slowly changing) → YAML config (Python side)
- Compute job (sim, optimization, ML) → Python service with three entry points
If it doesn't match one, that's the finding — name it.
- One-shot or scheduled CSV → TS script in
-
TS or Python? Default: Next.js side (TS). Move to Python when:
- Numeric / scientific libraries are non-trivial (geopandas, shapely, numpy/scipy)
- Existing Python expertise / models
- Compute runtime > Vercel function timeout (~10s on hobby, 60s on pro)
-
Storage shape? Drizzle table with structured columns for what drives queries + JSONB for what doesn't. Rule: if you need to filter or sort by it at app speed, it earns a column.
-
Deployment shape?
- TS script → run locally or in GitHub Action; commits the data to DB
- Cloud Run API → HTTP endpoint, FastAPI, API key dependency
- Cloud Run Pub/Sub handler → async job processor
- Long-running compute → Cloud Run with extended timeout, or Cloud Run Jobs
-
Migrations? Run in CI, not at runtime. Drizzle's generate + push, or dbmate for raw SQL projects.
-
Idempotency? Default to upsert-on-conflict for CSV imports. Wrap in a transaction. Don't assume "imported once."
-
Converter vs service split? Pure transforms in
*-converter.ts(client-safe). I/O in*-service.ts(server-only). Don't blur.
Reference: canonical TS import script
// scripts/data_processing/import-foo.ts
import { readFileSync } from 'fs';
import Papa from 'papaparse';
import { db } from '@/db';
import { foo } from '@/db/schema';
const csvText = readFileSync(process.argv[2], 'utf8');
const { data, errors } = Papa.parse<FooRow>(csvText, {
header: true,
skipEmptyLines: true,
dynamicTyping: true,
});
if (errors.length) {
console.error('Parse errors:', errors);
process.exit(1);
}
await db.transaction(async (tx) => {
for (const row of data) {
await tx.insert(foo).values({
externalId: row.external_id,
name: row.name,
// ... map every column
}).onConflictDoUpdate({
target: foo.externalId,
set: { name: row.name, updatedAt: new Date() },
});
}
});
console.log(`Imported ${data.length} rows`);
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.
- 7d ago First seen · 146 lines · 103 tokens per session scan A 8191de7be481
factory-data-pipeline-engineer is a skill published in the GitHub repository nonlinear-xyz/factory-kit (9 stars, last pushed 1mo ago), licensed MIT. It adds 103 tokens to every session and 1,468 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 skills, from other repositories
gemini-webhooks
Receive and verify Google Gemini API webhooks. Use when setting up Gemini webhook handlers for batch jobs, video generation, or Interactions API function-calling LROs, debugging signature verification, or handling events like batch.succeeded, batch.failed, video.generated, or interaction.completed.
llm-pipeline
Use when wiring several LLM calls into a production flow: typed contracts between steps, a router/gateway so 429s, timeouts and outages fail over instead of taking you down, and cost control via caching, model tiers and abort caps. NOT single-prompt wording (that is prompt-engineering), NOT a model-driven tool loop…
azure-cognitive-search
Expert knowledge for Azure AI Search development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when designing indexes, skillsets, indexers, vector/semantic search, or secure data…
azure-speech
Expert knowledge for Azure Speech in Foundry Tools development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when building STT/TTS containers, custom voices, avatars/visemes, telephony/agents, or batch synthesis…
prompt-sensei
Stage-aware prompt coaching, prompt improvement, lookback analysis, prompting habit feedback, and local reports about prompt quality for AI coding agents such as Claude Code or Codex.
azure-data-manager-for-agri
Expert knowledge for Azure Data Manager for Agriculture development including limits & quotas, security, configuration, and integrations & coding patterns. Use when setting up BYOL creds/Private Link, ag data ingestion/IoT, AI/nutrient APIs, throttling, or Event Grid logs, and other Azure Data Manager for Agriculture…