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 pipeline-autogit 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-auto)<a href="https://agentmods.dev/skills/kardebadas/claude-plugin/pipeline-auto"><img src="https://agentmods.dev/badge/skills/kardebadas/claude-plugin/pipeline-auto/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-auto"><img src="https://agentmods.dev/badge/skills/kardebadas/claude-plugin/pipeline-auto.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.00093 | $0.03830 |
| Opus 5.5 | $0.00037 | $0.01532 |
| Sonnet 5.5 | $0.00019 | $0.00766 |
| Haiku 4.5 | $0.00009 | $0.00383 |
Grade A, and why
pipeline-auto 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 21d 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pipeline-auto: controller rules
Machines may unblock work. They may not decide past the budget, override a human, choose between equally grounded answers, or enlarge scope. When a rule says escalate, escalating is the decisive action. Deadline, billing and "too cautious" pressure change none of these rules.
The rule this skill reverses
superb:pipeline forbids "a Brain Agent that decides user requirements"
(skills/pipeline/references/planning.md:177-181), and its zero-assumption law
(skills/pipeline/SKILL.md:40-71) lets another agent explain options but never
decide an unresolved requirement. This skill is that Brain Agent, built on
purpose. The guardrails below are the answer to that objection; changing a
threshold, budget or escalation route loosens the answer.
| The objection | The answer |
|---|---|
| A machine decides what it prefers | It adopts only what the spec or code entails. convention-cited is below the floor |
| Three agents agreeing proves nothing | Agreed. The bar is grounding rung, not votes; reading assignments decorrelate the three |
| It will decide more and more | 3 adoptions per phase, 10 per run, checked before dispatch; only a human extends, at most twice |
| It will overrule the user | A candidate contradicting Provenance: human is rejected at any rung |
| It will build what nobody asked for | Stage 06 seals the phase set; the tracker creates phases only at stage 07 and only for sealed ids (the ids themselves are not checked against the master plan); MISSING-FROM-SPEC is frozen |
| It will drift from the request | Depth cap 2 from the last human answer |
| It grades its own homework | Every adoption is labelled Provenance: quorum; the terminal report leads with them, weakest first |
Want the user consulted at each decision? Use superb:pipeline. This is a
different trade, not a better version.
Invocation
Trim $ARGUMENTS and select exactly one mode:
| Argument | Mode |
|---|---|
| empty | Full run from stage 01 |
resume |
Resume one compatible pipeline-auto/v1 run from its files and Git. Never create or replace a run |
status |
Strictly read-only: no lock, write, reconcile, dispatch, test, fix or initialize |
| anything else | Ask what the user meant. Do not guess a verb |
What ships with it
51 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 69 KB runs code
- prompts/adversarial-reviewer.md 4.1 KB
- prompts/brain-proposal.md 6.3 KB
- prompts/brain.md 6.3 KB
- prompts/implementer.md 7.2 KB
- prompts/task-reviewer.md 7.2 KB
- README.md 3.3 KB
- references/execution.md 15 KB
- references/persistence.md 8.4 KB
- references/planning.md 8.7 KB
- references/quorum.md 22 KB
- references/review.md 9.7 KB
- scripts/pipeline_auto_state.py 1018 KB runs code
- scripts/review-package 2.8 KB
- scripts/sdd-workspace 2.4 KB
- scripts/task-brief 2.5 KB
- templates/completeness-proposals.md 1.7 KB
- templates/decisions.md 8.9 KB
- templates/findings.md 3.0 KB
- templates/progress.md 2.5 KB
- templates/task-brief.md 1.4 KB
- templates/verification-evidence.md 3.2 KB
- templates/worker-report.md 2.0 KB
- templates/worker-result.md 3.6 KB
- tests/check_baseline_evidence.py 9.7 KB runs code
- tests/fixtures/quorum/question-record.md 1.5 KB
- tests/fixtures/README.md 1.1 KB
- tests/fixtures/valid-progress.md 6.1 KB
- tests/pressure/.gitignore 1.2 KB
- tests/pressure/GREEN-baseline.md 22 KB
- tests/pressure/oracles.md 23 KB
- tests/pressure/PRESSURE-SUFFIX.md 413 B
- tests/pressure/RED-baseline.md 55 KB
- tests/pressure/stimuli/S01.md 1.1 KB
- tests/pressure/stimuli/S02.md 1.4 KB
- tests/pressure/stimuli/S03.md 1.2 KB
- tests/pressure/stimuli/S04.md 1.1 KB
- tests/pressure/stimuli/S05.md 1.3 KB
- tests/pressure/stimuli/S06.md 953 B
- tests/pressure/stimuli/S07.md 885 B
- tests/pressure/stimuli/S08.md 839 B
- tests/pressure/stimuli/S09.md 1.2 KB
- tests/pressure/stimuli/S10.md 1.0 KB
- tests/test_baseline_evidence.py 13 KB runs code
- tests/test_controller_walkthrough.py 2.0 KB runs code
- tests/test_oracle_disclosure_order.py 14 KB runs code
- tests/test_pipeline_auto_state.py 1097 KB runs code
- tests/test_pressure_stimuli.py 4.2 KB runs code
- tests/test_record_template_ignored.py 3.7 KB runs code
- tests/test_skill_structure.py 16 KB runs code
- tests/test_task_lifecycle.py 1059 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.
- 21d ago First seen · 267 lines · 93 tokens per session scan A b1aa8c95cbca
pipeline-auto is a skill published in the GitHub repository kardebadas/claude-plugin (3 stars, last pushed 18d ago), licensed Apache-2.0. It adds 93 tokens to every session and 3,830 once invoked, about $0.0004 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-09-24.
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.
delete
Preview and permanently delete a NeatContext context while preserving any externally linked knowledge folder. Use only when the user explicitly invokes this skill or clearly asks to delete a context.
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.