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 gustavo-meilus/superpipelines --skill adding-a-pipeline-stepgit clone --depth 1 https://github.com/gustavo-meilus/superpipelinesWrote 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/gustavo-meilus/superpipelines/adding-a-pipeline-step)<a href="https://agentmods.dev/skills/gustavo-meilus/superpipelines/adding-a-pipeline-step"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/superpipelines/adding-a-pipeline-step/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/gustavo-meilus/superpipelines/adding-a-pipeline-step"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/superpipelines/adding-a-pipeline-step.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.00964 |
| Opus 5 | $0.00012 | $0.00482 |
| Sonnet 5 | $0.00005 | $0.00193 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
adding-a-pipeline-step 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 10d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adding a Pipeline Step — Mutation Workflow
Workflow Phases
PHASE 1: INSERTION DESIGN
- Identify the insertion point (Before/After/Parallel/Append) and affected neighbors.
- Apply the 4D Method to define the new step's intent, inputs, and outputs.
- Determine the component type: Skill-only, Skill + Agent, or Reuse Existing.
PHASE 2: ARCHITECTED STAGING
- Dispatch
pipeline-architectinSTEP-ADDmode to generate new artifacts. - All new artifacts MUST be written to
{ROOT}/superpipelines/temp/{P}/edit-{ts}/for staging. NEVER write directly to production paths during design.
PHASE 3: TOPOLOGY VALIDATION
- Verify the staged
topology.jsonfor:- Unique Step ID.
- Valid
depends_onreferences. - Schema compatibility between predecessor outputs and new step inputs.
- Failures: Return to the Architect with specific error logs.
PHASE 4: DELTA AUDIT
- Dispatch
pipeline-auditorinDELTAmode on all staged files (components, topology, and entry skill). - If the audit returns SEV-0 or SEV-1 findings, remediate and re-audit. Do NOT proceed to promotion until the delta is clear.
PHASE 5: PROMOTION & REGISTRATION
- Present the updated topology and audit results for human approval (
AskUserQuestion). - Upon
APPROVE, move staged files to their final absolute paths in agents, skills, and pipeline directories. - Update the
registry.jsonlists to include new components. - Version Stamp: Update
plugin_versionintopology.json, the registry entry, and the new agent's frontmatter to the current superpipelines version.
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.
- 10d ago First seen · 76 lines · 24 tokens per session scan A a9092596bbb6
adding-a-pipeline-step is a skill published in the GitHub repository gustavo-meilus/superpipelines (4 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 964 once invoked, about $0.0001 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.
Other skills, from other repositories
PR Description Writer
Writes clear, thorough pull request descriptions from a diff or list of changes.
cog-braindump-capture
Capture raw thoughts with automatic domain classification and vault routing.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
context-engineering
Dynamic context injection, mode switching (dev/review/research), selective loading, and strategic compaction for token optimization.