plumber-execute

plumber-execute is a skill for Claude Code, Codex from LUKAWI/super-plumber. It costs 152 tokens per session (3,829 once invoked), scanned A, original, MIT.

A guided execution skill for running an approved task topology, a dependency map of work, from start to finish. It claims tasks, performs them, reports checkpoints, and verifies the final result.

In plain words
What is it for?
Use it after a topology has been designed and approved to execute its nodes, coordinate subagents or solo work, retry failures, and confirm the finished build.
Why use it?
It provides a controlled process for executing tasks in order and handling parallel work or failures. It separates approved planning from implementation and final checks.

Skill for Claude CodeCodex

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 skills/lukawi/super-plumber/plumber-execute
Any agent
npx skills add LUKAWI/super-plumber --skill plumber-execute
Clone the repo
git clone --depth 1 https://github.com/LUKAWI/super-plumber

Made for: Claude Code, Codex.

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 plumber-execute

README.md
[![agentmods](https://agentmods.dev/badge/skills/lukawi/super-plumber/plumber-execute.svg)](https://agentmods.dev/skills/lukawi/super-plumber/plumber-execute)
Your own site
<a href="https://agentmods.dev/skills/lukawi/super-plumber/plumber-execute"><img src="https://agentmods.dev/badge/skills/lukawi/super-plumber/plumber-execute.svg" alt="Measured on agentmods" height="20"></a>
Per session 152 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,829 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.00152 $0.03829
Opus 5 $0.00076 $0.01914
Sonnet 5 $0.00030 $0.00766
Haiku 4.5 $0.00015 $0.00383

Measured today against content hash 4c334036eba8, 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 today.

The scan reads SKILL.md. This mod also ships 7 executable files (scripts/sp-checkpoint.mjs, scripts/sp-claim.mjs, scripts/sp-core.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.pi/skills/plumber-execute/SKILL.md · 159 lines

How it starts

The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plumber Execute — 主线程编排剧本:拓扑执行 → 全部 passed → 三层验收

Overview

按依赖顺序执行每个节点:CLAIM → WORK → 逐 checkpoint 上报 → execution_report → passed;全部 passed 后做三层验收,验证构建成果真实完整。本页是编排剧本:每步只留一句纪律,全部调用语法、字段含义与报错修法统一看 Operations 手册(寻址约定见手册 §11)。

产出物 = 全部节点 passed 且验收通过的构建成果,不是设计。图还没设计/未审核 → 回 plumber-design


When to Use

  • 拓扑图已设计并审核通过,开始执行节点任务
  • 需要 claim 节点 / 上报 checkpoint / 提交 execution_report / 状态流转
  • 需要判断这批节点串行还是派 subagent 并行
  • 需要验证全部节点 passed、构建成果完整;节点 failed → 走重试链重新调度

衔接关系(subagent 与 skill 已解耦,不再是 REQUIRED SUB-SKILL)

  • 执行协议的工具调用语法与并行数据判读法 → 手册 §4;状态机七态与三条硬规则 → 手册 §5——本 skill 只留骨架与纪律,绝不复述语法。
  • 图未设计或未审核通过 → plumber-design
  • 派 executor subagent → 按「派单模板」;检测不到可用 subagent → 走「solo 分支」。
  • 节点状态裁决 / checkpoint 聚合 / 输出抽查 → super-mario agent。

执行协议(每节点 0–5 步,严格按序;各步调用语法统一 → 手册 §4.1)

  1. PLAN — 每轮决策前先看 graph_get_next_actions 五桶;冷启动第一步从 ready_eligible 拿入口节点(门禁已满足的 pending/failed 转 ready 即执行),不要拿 get_graph+search 手工拼数据。
  2. CLAIM只 claim ready 节点(eligible 先 {status:"ready"} 再 claim),必带 claim_by,拿到 already claimed 就换节点别重试同节点;claim 响应附 governing_adrs 必读——adr_flags ⚠️ 出现即停:该节点依据的 ADR 已被接替,先弄清新决策再动手,ADR 状态只能由裁决方(super-mario/人类)改。
  3. WORK — 执行 plan.description,把 checkpoints 当逐条清单完成。
  4. REPORT AS YOU GO — 每完成一个 checkpoint 立即上报,绝不攒批——完成的未上报 = 丢失的进度。
  5. HAND OFF — 干完立刻填 execution_report:artifacts 只写真实文件路径(会被存在性核验),绝不编造路径。
  6. passed — 核心层硬门禁一句话:非空 report + checkpoint 全 passed/skipped + 无 failed 裁决,缺一即拒——铁律先 verdict 后 passed

重试链 / attempts 上限 / blocked 解除 / reclaim 细节 → 手册 §4.3 与 §5。

节点 passed 后的旅程告知(WF10,必做):passed 不是静默流转——向用户概述当前下一前沿(graph_get_next_actions 五桶读数:前沿在哪、还剩几张票);前沿有多个互不依赖的 ready 节点时,建议用户另开会话 /plumber-join 并行推进(并行判据见下文「并行决策」)。


work the graph 模式(program 档:工作会话解雾)

图带未毕业雾区(class=program)→ 本 skill 切 work 模式:不跑整图,按「取前沿 → 解一张 → 毕业雾 → 决议回写 → 交棒」循环——解票是为了把雾想清楚,不是为了清桶赶进度。

  1. 取前沿graph_get_next_actions 五桶(CLI graph next)里挑一张 research 票(雾 ignited 点过火、或 plan 自述调研目标);票照常 claim——票与雾之间没有边,点火关系在雾字段与 plan 文字里,不在拓扑上。
  2. 解一张:一次会话只解一张票,走满 0–5 步协议(claim→report 全循环);调研产物落真实 artifact,结论写进执行报告。
  3. 毕业雾:毕业条件达成 → CLI graph graduate-fog --produced <票id,票id> --reason "<结论摘要>";MCP graph_graduate_fog {produced, reason}。毕业 = 清除 fog + fog_graduated 事件,无雾时报错(毕业是事实陈述,不是清理操作)。毕业属结构修订,按 DEC-7 amend 协议执行(影响评估 + 增量人审;命令自带守卫:自动快照、graph_amended 事件、review 回置 unreviewed)——协议全文不在此复制 → plumber-design amend 模式与手册 §2.2。
  4. 决议回写:结论够 ADR 三判据 → graph adr create(MCP graph_create_adr)落 proposed,accept/supersede 归裁决方(super-mario/人);术语沉淀进所属 context 顶点 glossary。
  5. to-standard 交棒:雾清零 → graph update-graph --class standard,图回常规档;其余节点回归上文标准执行协议(0–5 步 + 三层验收)。

Read the full file on GitHub · 159 lines

Files

What ships with it

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

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. today Changed · +30 lines 4c334036eba8
  2. 4d ago First seen · 129 lines · 152 tokens per session scan A 825c822cf466

Subscribe to this mod's changes

plumber-execute is a skill published in the GitHub repository LUKAWI/super-plumber (2 stars, last pushed yesterday), licensed MIT. It adds 152 tokens to every session and 3,829 once invoked, about $0.0008 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens