Borrowing it
Nothing to install: this file belongs to junghwaYang/oh-my-codex. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/junghwaYang/oh-my-codex/main/.codex/skills/pipeline/SKILL.mdgit clone --depth 1 https://github.com/junghwaYang/oh-my-codexWrote 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/junghwayang/oh-my-codex/pipeline)<a href="https://agentmods.dev/skills/junghwayang/oh-my-codex/pipeline"><img src="https://agentmods.dev/badge/skills/junghwayang/oh-my-codex/pipeline.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.00000 | $0.00648 |
| Opus 5 | $0.00000 | $0.00324 |
| Sonnet 5 | $0.00000 | $0.00130 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
pipeline 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 6d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Skill
Sequential, staged processing for multi-step transformations.
When to Use
- Multi-step data transformations
- Sequential processing with dependencies
- Workflows with strict ordering
- Build/deploy pipelines
When NOT to Use
- Independent parallel tasks (use ultrawork)
- Simple single-step operations
- Tasks without dependencies
Pipeline Concept
Stage 1 → Stage 2 → Stage 3 → Stage 4 → Output
│ │ │ │
└─────────┴─────────┴─────────┘
Each stage depends on previous
Pipeline Definition
pipeline:
name: "Feature Implementation"
stages:
- name: plan
agent: planner
input: user_request
output: plan_document
- name: implement
agent: executor
input: plan_document
output: code_changes
- name: test
agent: tester
input: code_changes
output: test_results
- name: review
agent: reviewer
input: code_changes
output: review_feedback
- name: document
agent: writer
input: code_changes
output: documentation
Stage Types
Transform
Input → Processing → Output
Validate
Input → Check → Pass/Fail
Branch
Input → Condition → Path A or Path B
Aggregate
Multiple Inputs → Combine → Single Output
Built-in Pipelines
Feature Pipeline
plan → implement → test → review → document → deploy
Bug Fix Pipeline
reproduce → diagnose → fix → test → review
Refactor Pipeline
analyze → plan → refactor → test → review
Migration Pipeline
assess → plan → migrate → verify → cleanup
Usage
pipeline: implement user authentication
- plan the feature
- implement backend
- implement frontend
- write tests
- document API
pipeline: migrate from REST to GraphQL
Error Handling
On stage failure:
1. Log error context
2. Attempt retry (configurable)
3. If still failing:
- Option A: Stop pipeline
- Option B: Skip to next stage
- Option C: Rollback previous stages
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.
- 6d ago First seen · 135 lines · 0 tokens per session scan A 51a6e25bf9f9
pipeline is a skill published in the GitHub repository junghwaYang/oh-my-codex (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 648 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…