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.
git 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/commands/gustavo-meilus/superpipelines/delete-step)<a href="https://agentmods.dev/commands/gustavo-meilus/superpipelines/delete-step"><img src="https://agentmods.dev/badge/commands/gustavo-meilus/superpipelines/delete-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/commands/gustavo-meilus/superpipelines/delete-step"><img src="https://agentmods.dev/badge/commands/gustavo-meilus/superpipelines/delete-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.00034 | $0.00344 |
| Opus 5.5 | $0.00014 | $0.00138 |
| Sonnet 5.5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
delete-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 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.
What it actually says
Delete Step — Command Entry
Invoke the deleting-a-pipeline-step skill. The skill owns the full protocol (PHASE 0 pipeline & step selection → PHASE 1 gap analysis → PHASE 2 mutation design / rewire → PHASE 3 delta audit → PHASE 4 human approval → PHASE 5 atomic promotion).
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 First seen · 22 lines · 34 tokens per session scan A 5840728dc33f
delete-step is a command published in the GitHub repository gustavo-meilus/superpipelines (4 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 344 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 commands, from other repositories
refactor
Refactor $ARGUMENTS following modern JavaScript/TypeScript best practices.
review
A command for reviewing code with security checks and a check for compliance with MX tags. The available description does not explain what MX tags are.
task-conductor.skeleton
/task-conductor top 5 -> /task-conductor plan top 5 /task-conductor all -> /task-conductor plan all /task-conductor 3,5,8 -> /task-conductor plan 3,5,8.
review-module.skeleton
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects Example output.
bug-review.skeleton
Description: This section will be populated with data from Bootstrap's manifest files. Required manifest fields: project.description, stack.primary, project.structure Example output.
bug
Report a bug from a plain description — triggers investigation, structured documentation and fix coordination.