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 skills/new1direction/korgex/data-pipelinesnpx skills add New1Direction/korgex --skill data-pipelinesgit clone --depth 1 https://github.com/New1Direction/korgexWrote 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/new1direction/korgex/data-pipelines)<a href="https://agentmods.dev/skills/new1direction/korgex/data-pipelines"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/data-pipelines.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.00017 | $0.00358 |
| Opus 5 | $0.00009 | $0.00179 |
| Sonnet 5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
data-pipelines 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
A data pipeline moves/transforms data between systems. The failure modes are about correctness and recovery, not just throughput.
- Idempotent + resumable. Pipelines fail partway. Design so re-running produces the same result (upsert by key, not blind insert) and can resume from a checkpoint rather than restarting from zero.
- Validate at the edges. Check schema/types/ranges on ingest; decide up front what to do with bad records — reject, quarantine, or repair — never silently drop.
- Idempotency keys + watermarks. Track what's been processed (a high-water mark or per-record key) so incremental runs don't double-count or miss late data.
- Batch sensibly. Process in chunks with bounded memory; don't load an entire dataset into RAM. Stream where you can.
- Make it observable. Record counts in/out/rejected per stage; a pipeline that silently processes 0 rows is a common, costly bug. Alert on anomalies.
- Schema evolution. Upstream schemas change — handle added/removed fields gracefully (defaults, versioning) rather than crashing the whole run.
- Separate extract / transform / load so each stage is testable in isolation, and keep raw inputs so you can reprocess after a transform bug.
Red flag: a non-resumable pipeline that must restart from scratch on any failure, or one with no record counts so you can't tell correct from silently-empty.
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 · 29 lines · 17 tokens per session scan A 14366926ed4b
data-pipelines is a skill published in the GitHub repository New1Direction/korgex (5 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 358 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-31.
Other skills, from other repositories
vibe-ui-design
Use when designing UI/UX, defining design systems, choosing color palettes, typography, spacing, or component primitives. Triggers on "design system", "design tokens", "color palette", "UI 设计", "深色工业风", "design language".
vibe-security
Use when performing security audits, vulnerability scanning, dependency checks, or secure code reviews. Triggers on "security audit", "scan vulnerabilities", "安全审查", "漏洞扫描", "OWASP", "dependency check".
vibe-ui-beautify
Use when adding animations, micro-interactions, 3D effects, glassmorphism, or "juicy" tactile feedback to UI components. Triggers on "animation", "hover effect", "transition", "动效", "果汁感", "Framer Motion", "GSAP", "3D 视效".
vibe-plan
Use this skill to create a phased development plan based on requirements, architecture, and API docs.
vibe-test
Use when writing tests, performing unit testing, integration testing, or verifying system functionality. Triggers on "write tests", "run tests", "add unit test", "TDD", "测试", "跑测试".
vibe-autopilot
Use this skill when the user requests fully autonomous, 24/7 hands-free development without human intervention.