Borrowing it
Nothing to install: this file belongs to LUKAWI/super-plumber. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/LUKAWI/super-plumber/master/.pi/skills/plumber-join/SKILL.mdgit clone --depth 1 https://github.com/LUKAWI/super-plumberWrote 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/lukawi/super-plumber/plumber-join)<a href="https://agentmods.dev/skills/lukawi/super-plumber/plumber-join"><img src="https://agentmods.dev/badge/skills/lukawi/super-plumber/plumber-join.svg" alt="Measured on agentmods" 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.00095 | $0.00645 |
| Opus 5 | $0.00048 | $0.00322 |
| Sonnet 5 | $0.00019 | $0.00129 |
| Haiku 4.5 | $0.00010 | $0.00064 |
Grade A, and why
plumber-join 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 yesterday.
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
Plumber Join — 最小上下文入场
目的只有两个：知道在开发什么，知道下一步开发什么。终点是候选节点 ready，不是完成节点。
入场流程
- 定位工作区与图：读取工作区入口说明；用户指名图则直接使用，否则
graph_list_graphs选择明确的目标，有歧义才询问。MCP 用进程级graph_switch；CLI 用显式--graph <图名>，不切换共享 active 图。 - 了解目标与进度：读取目标图的 entry/exit、审核记录及进度摘要，调用一次
graph_get_next_actions查看前沿。已有信息直接复用；不把 pending/ready/running 当作已审核证据，也不把全 passed 当作整体验收完成。 - 确定下一步：优先指定的可执行节点，否则在 ready 桶按 priority（数值越小越先）选择，ready 空再选 ready_eligible。只读取候选节点的 plan、DoD、checkpoints 及其直接关联的 context/ADR；按需打开相关文件，不通读整库、历史记录或整本手册。发现 adr_flags 时先澄清现行决策。
- 准备就绪即结束：确认候选范围已获审核（quick 可用 self 凭据），ready 节点不重复写；ready_eligible 节点用
graph_update_node_status {id, status:"ready"}交门禁复校。失败如实报告，不 force、不绕过。无可执行前沿则说明阻塞、正在执行或待验收情况后结束。
交接
简短交付：图名 / 正在开发什么 / 当前进度 / 下一节点及 ready 状态 / 必要上下文路径和约束。
用户原请求已包含执行授权时，结束本技能后自然转 plumber-execute，由它重新确认前沿并 claim；仅要求了解进度或入场时，在此停止，不擅自开发。纯查询不修改节点状态。
边界：不 claim、不 reclaim、不开发、不上报 checkpoint/report、不写 verdict/passed、不循环认领。未审核则说明需 plumber-design 完成审核；操作语法或错误处理有疑问时才查 integrations/shared/manual.md §4/§5/§9。不手改 .graph/ YAML。
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.
- yesterday Changed · -29 lines · -57 tokens per session 411e3dc0d7bd
- 4d ago First seen · 53 lines · 152 tokens per session scan A 6ea54ffbaa6f
plumber-join is a skill published in the GitHub repository LUKAWI/super-plumber (3 stars, last pushed yesterday), licensed MIT. It adds 95 tokens to every session and 645 once invoked, about $0.0005 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-09-04.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.