optimize-pipeline

optimize-pipeline is a command for Claude Code from gustavo-meilus/superpipelines. It costs 41 tokens per session (311 once invoked), scanned A, original, MIT.

A command for improving an existing named pipeline, meaning an automated sequence of processing steps. It examines the pipeline, agrees an optimization plan with you, applies the changes together, and audits the result.

In plain words
What is it for?
Use it to review pipeline structure and past runs, decide on improvements, apply them as one batch, and check the outcome.
Why use it?
It helps identify wasted model usage, cost, or inefficient steps without changing the pipeline before a plan is agreed.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the superpipelines plugin — 54 skills, 10 commands, 14 agents, 4 hooks shipped together

Good fit Use it to review pipeline structure and past runs, decide on improvements, apply them as one batch, and check the outcome.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/gustavo-meilus/superpipelines/optimize-pipeline
Install

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.

Clone the repo
git clone --depth 1 https://github.com/gustavo-meilus/superpipelines

Made for: Claude Code.

Or install superpipelines, the plugin that ships this one along with the rest of its 54 skills, 10 commands, 14 agents, 4 hooks.

Wrote 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.

agentmods badge for optimize-pipeline

README.md
[![agentmods](https://agentmods.dev/badge/commands/gustavo-meilus/superpipelines/optimize-pipeline/github.svg)](https://agentmods.dev/commands/gustavo-meilus/superpipelines/optimize-pipeline)
Your own site
<a href="https://agentmods.dev/commands/gustavo-meilus/superpipelines/optimize-pipeline"><img src="https://agentmods.dev/badge/commands/gustavo-meilus/superpipelines/optimize-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.

agentmods 80×15 button for optimize-pipeline

Your own site · 80×15
<a href="https://agentmods.dev/commands/gustavo-meilus/superpipelines/optimize-pipeline"><img src="https://agentmods.dev/badge/commands/gustavo-meilus/superpipelines/optimize-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 311 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.00311
Opus 5 $0.00020 $0.00156
Sonnet 5 $0.00008 $0.00062
Haiku 4.5 $0.00004 $0.00031

Measured 8d ago against content hash 08c8cd967a64, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

optimize-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 8d 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.

commands/optimize-pipeline.md · 23 lines

What it actually says

Optimize Pipeline — Command Reference

Runs the on-demand optimization workflow against an existing named pipeline: a read-only pipeline-optimizer survey across four axes, a 4D → brainstorm → grill discovery session that locks an optimization_plan, and an atomic batch-apply gated by pipeline-auditor.

Changes

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.

  1. 8d ago First seen · 23 lines · 41 tokens per session scan A 08c8cd967a64

Subscribe to this mod's changes

optimize-pipeline is a command published in the GitHub repository gustavo-meilus/superpipelines (4 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 311 once invoked, about $0.0002 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-08-31.