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 kardebadas/claude-plugin --skill pipelinegit clone --depth 1 https://github.com/kardebadas/claude-pluginWrote 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/kardebadas/claude-plugin/pipeline)<a href="https://agentmods.dev/skills/kardebadas/claude-plugin/pipeline"><img src="https://agentmods.dev/badge/skills/kardebadas/claude-plugin/pipeline/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kardebadas/claude-plugin/pipeline"><img src="https://agentmods.dev/badge/skills/kardebadas/claude-plugin/pipeline.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.02160 |
| Opus 5.5 | $0.00010 | $0.00864 |
| Sonnet 5.5 | $0.00005 | $0.00432 |
| Haiku 4.5 | $0.00002 | $0.00216 |
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 1mo 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Superb Pipeline
Purpose
Pipeline is a thin controller around Superpowers. It keeps the approved design, plans, decisions, execution state, and evidence in project files so a compacted or restarted session can continue without inventing requirements or repeating work.
The controller owns orchestration and durable transitions. It does not reimplement the skills that investigate, plan, implement, debug, review, and verify the work.
Invocation
Trim whitespace from this complete argument string, then select exactly one mode:
$ARGUMENTS
| Argument | Mode |
|---|---|
| empty | Full run: begin with planning. |
resume |
Resume one compatible v2 run from its files and Git evidence. Never create or replace a run. |
status |
Strictly read-only inspection. Do not lock, write, reconcile, dispatch, test, fix, or initialize. |
| anything else | Stop and ask what the user meant. Do not guess a verb or expose an internal remediation mode. |
Use the whole argument string, never an indexed positional placeholder.
For resume or status, use references/persistence.md.
If no run is identifiable, report that. If multiple runs qualify, ask the user
which one. Recency is not selection authority.
Zero-assumption law
Before making any required decision, inspect these sources in order:
- the user's explicit instructions;
- recorded explicit user answers;
- the approved design/specification;
- the approved master plan and phase plans;
- explicit written repository rules.
If they explicitly answer the question, cite and follow the answer. If they do not, or they conflict:
- stop only the affected work;
- record the exact question and blocked task/gate;
- ask the user and wait;
- persist the explicit answer;
- update affected approved artifacts transparently when required;
- resume through the validated controller transition.
Another agent may investigate facts and explain options, but it cannot decide an unresolved requirement for the user. Generic approval or “continue” does not answer a choice. Do not ask again when an explicit applicable answer is already recorded.
What ships with it
34 files 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.
- examples/controller_walkthrough.py 8.8 KB runs code
- README.md 8.1 KB
- references/execution.md 12 KB
- references/persistence.md 12 KB
- references/planning.md 9.9 KB
- references/review.md 17 KB
- scripts/pipeline_state.py 255 KB runs code
- templates/artifact-remediation-evidence.md 359 B
- templates/decisions.md 2.2 KB
- templates/findings.md 164 B
- templates/fix-plan.md 2.7 KB
- templates/progress.md 1.7 KB
- templates/verification-evidence.md 516 B
- templates/worker-result.md 750 B
- tests/fixtures/conflicting-result.md 560 B
- tests/fixtures/legacy-v1-progress.md 243 B
- tests/fixtures/malformed-unknown-field.md 1.5 KB
- tests/fixtures/malformed-v2-progress.md 128 B
- tests/fixtures/malformed-worker-result.md 561 B
- tests/fixtures/missing-marker.md 102 B
- tests/fixtures/phase-plan-invalid-metadata.md 558 B
- tests/fixtures/phase-plan-valid.md 772 B
- tests/fixtures/pre-adoption-v2-progress.md 2.5 KB
- tests/fixtures/pressure/extract_phase04_stimulus.py 1.3 KB runs code
- tests/fixtures/pressure/phase-04-worker-stimuli.md 3.6 KB
- tests/fixtures/README.md 979 B
- tests/fixtures/stale-result.md 552 B
- tests/fixtures/unknown-schema.md 85 B
- tests/fixtures/valid-artifact-worker-result.md 679 B
- tests/fixtures/valid-result-done.md 577 B
- tests/fixtures/valid-result-needs-context.md 553 B
- tests/fixtures/valid-source-worker-result.md 630 B
- tests/fixtures/valid-v2-progress.md 2.8 KB
- tests/test_pipeline_state.py 340 KB runs code
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.
- 1mo ago Changed · -1,227 lines · -56 tokens per session 54fe1061c4a5
- 1mo ago Changed · +87 lines edf006c7042f
- 1mo ago Changed · +130 lines ed46e240e27b
- 1mo ago Changed · +211 lines 2f4010563745
- 1mo ago Changed · +213 lines 455a78348899
- 1mo ago First seen · 812 lines · 80 tokens per session scan A 8d4b19726a87
pipeline is a skill published in the GitHub repository kardebadas/claude-plugin (3 stars, last pushed 21d ago), licensed Apache-2.0. It adds 24 tokens to every session and 2,160 once invoked, about $0.0001 per session on Opus 5.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
import
Import a self-contained NeatContext context bundle shared by another person, or reconcile a newer copy of a context already on this machine, leaving the source bundle unchanged. Use only when the user explicitly invokes this skill or asks to import a NeatContext bundle.
save
Save durable decisions, findings, plans, and implementation knowledge from the visible Codex conversation into a new or existing NeatContext context. Use only when the user explicitly invokes this skill or asks to preserve the current conversation as reusable context.
create
Create a fresh NeatContext context from a user-defined behavioral profile and an existing local knowledge folder. Use only when the user explicitly invokes this skill or asks to create a new context rather than save the current conversation.
extensions
Report which extensions the connected NeatContext context expects, and whether this machine provides them. Use when the user asks what a context can reach, why an extension tool is missing, or how to connect one here.
export
Export a NeatContext context saved from a conversation into a self-contained bundle folder that can be shared or moved to another machine. Use only when the user explicitly invokes this skill or asks to export a NeatContext context.
use
Connect or switch Codex to a local NeatContext Context by name or list number. Use only when the user explicitly invokes this skill, names a context to connect, or agrees to a routing suggestion.