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 turbo-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/turbo-pipeline)<a href="https://agentmods.dev/skills/kardebadas/claude-plugin/turbo-pipeline"><img src="https://agentmods.dev/badge/skills/kardebadas/claude-plugin/turbo-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/turbo-pipeline"><img src="https://agentmods.dev/badge/skills/kardebadas/claude-plugin/turbo-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.00114 | $0.04523 |
| Opus 5.5 | $0.00046 | $0.01809 |
| Sonnet 5.5 | $0.00023 | $0.00905 |
| Haiku 4.5 | $0.00011 | $0.00452 |
Grade A, and why
turbo-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 17d 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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Turbo Pipeline
Overview
Request → targeted exploration → one batch of at most six questions → spec → plan → subagent-driven implementation → whole-feature review/fix loop → done. The user is consulted once, at the start. Everything after the batch is decided from evidence, and where evidence runs out, by two independent Turbo Brains whose higher-confidence answer wins.
This is a thin router over Superpowers skills plus superb:bug-fix. It adds no
run files, no controller, no phase plans, no quorum budgets — and it removes no
review seat: fresh implementers, a task review after every task, and a
mandatory final review of the integrated feature. Less bureaucracy, not worse
engineering. The user's invocation of this skill is a standing instruction:
where a composed skill's default says to ask, present, or wait, the overrides
below win — user instructions outrank skills, and violating an override to
follow a sub-skill default is violating the user.
The gate contract
There is one human gate, stage 3. Once its answers are in:
NORMAL QUESTION TO USER = FORBIDDEN.
No "which do you prefer", "should I continue", "does this look right", "can you confirm", "how should I handle this", no spec approval, no plan approval, no executor choice, no status check, and no equivalent dressed up as a summary that ends in a question mark. An engineering or product question goes down the authority ladder and then to the Two-Brain Resolver.
The one exception is authorization, never engineering: an action the runtime, the repository's rules, tool policy or safety require a human to authorize — merging, pushing to a shared branch, publishing, deploying, destructive external operations, credential changes, payments, irreversible account actions. A Brain cannot grant those. During the run, leave such an action undone and finish everything else. The single place a human is asked for authorization is the stage-9 handover menu, after the report.
The authority ladder
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.
- 17d ago First seen · 305 lines · 114 tokens per session scan A 5260ebfa8041
turbo-pipeline is a skill published in the GitHub repository kardebadas/claude-plugin (3 stars, last pushed 18d ago), licensed Apache-2.0. It adds 114 tokens to every session and 4,523 once invoked, about $0.0005 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-28.
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.