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 JansenAnalytics/claudex --skill pipeline-runnergit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote 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/jansenanalytics/claudex/pipeline-runner)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/pipeline-runner"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/pipeline-runner.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.00053 | $0.00984 |
| Opus 5 | $0.00026 | $0.00492 |
| Sonnet 5 | $0.00011 | $0.00197 |
| Haiku 4.5 | $0.00005 | $0.00098 |
Grade A, and why
pipeline-runner 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Runner Skill
Overview
Execute multi-step pipelines defined in JSON with:
- Sequential and parallel stages
- Dependency chains (
needs) - Conditional execution (
if) - Retries with backoff
- Timeouts per step
- Variable passing between steps (stdout → env var)
- Failure handling (
on_fail: continue|notify) - Run history and logs
Script
node ${CLAUDE_SKILLS_DIR:-$HOME/.claude-agent/.claude/skills}/pipeline-runner/scripts/pipeline.cjs <command> [args]
Commands
pipeline run <file.json> [--dry-run] [--var key=value] — Execute a pipeline
pipeline validate <file.json> — Validate syntax
pipeline list — List saved pipelines
pipeline history [--limit 10] — Recent runs
pipeline show-run <run-id> — Run details
Pipeline Format (JSON)
{
"name": "my-pipeline",
"env": { "MY_VAR": "value" },
"steps": [
{
"name": "build",
"run": "npm run build",
"timeout": 120,
"retries": 2,
"retry_delay": 5
},
{
"name": "test",
"needs": ["build"],
"run": "npm test",
"on_fail": "continue"
},
{
"name": "deploy",
"needs": ["test"],
"if": "steps.test.exitCode == 0",
"run": "./deploy.sh"
},
{
"name": "checks",
"parallel": [
{ "name": "lint", "run": "npm run lint" },
{ "name": "typecheck", "run": "tsc --noEmit" }
]
}
]
}
Step Properties
| Property | Type | Default | Description |
|---|---|---|---|
name |
string | required | Unique step identifier |
run |
string | — | Shell command to execute |
needs |
string[] | — | Steps that must complete first |
if |
string | — | Condition: steps.NAME.exitCode == 0 |
timeout |
number | 300 | Seconds before kill |
retries |
number | 0 | Retry count on failure |
retry_delay |
number | 5 | Seconds between retries |
on_fail |
string | halt | continue or notify or halt |
parallel |
step[] | — | Run sub-steps in parallel |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 139 lines · 53 tokens per session scan A 196e43742fa3
pipeline-runner is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 984 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
dev-soft-agent
Automated software development pipeline. Scans projects, prioritizes tasks, analyzes code, and orchestrates development loops. Zero dependencies (Python stdlib only).
magazine-web-ppt
For marketing and gtm work: bind launches, campaigns, events, and brand plans to growth and pipeline outcomes. Built around the core query "annual-marketing-plan", with GTM strategy lead judgment, buyer-ready proof, and this outcome: approve launch plan, campaign budget, or GTM motion.
html-ppt-zhangzara-coral
OpenDesign's community-growth campaign across GitHub, Discord, and X: the loops, the content calendar, and the pipeline math. Built as a decision-grade marketing & GTM deck for growth team, community lead.
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
feature-spec
Creates a complete product feature specification with acceptance criteria, scope, dependencies, and risks. Delegates to the Prometeo (PM) agent.