plumber-execute

A command that executes the tasks in an approved topology graph, a map showing task dependencies, in the required order. It tracks each task through claims, checkpoints, reports, and completion.

In plain words
What is it for?
Use it to run an approved `.graph/` task map, coordinate solo or parallel execution, retry failed tasks, and verify that all nodes passed.
Why use it?
It prevents dependent tasks from running before their prerequisites. It also supports parallel work when suitable and checks the completed build at three levels.

Command

Part of the super-plumber plugin — 2 commands, 1 MCP server shipped together

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.

agentmods
npx agentmods add commands/lukawi/super-plumber/plumber-execute
Clone the repo
git clone --depth 1 https://github.com/LUKAWI/super-plumber

Or install super-plumber, the plugin that ships this one along with the rest of its 2 commands, 1 MCP server.

Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 540 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00039 $0.00540
Opus 5 $0.00019 $0.00270
Sonnet 5 $0.00008 $0.00108
Haiku 4.5 $0.00004 $0.00054

Measured 2d ago against content hash 462a67323ae9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

plumber-execute 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 2d 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.

integrations/plugin/commands/plumber-execute.md · 27 lines

The source is not reproduced here

Licensed MIT

The repository is licensed MIT, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 2d ago First seen · 27 lines · 39 tokens per session scan A 462a67323ae9

Subscribe to this mod's changes

plumber-execute is a command published in the GitHub repository LUKAWI/super-plumber (2 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 540 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.