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/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/plugins/lukawi/super-plumber/plugin)<a href="https://agentmods.dev/plugins/lukawi/super-plumber/plugin"><img src="https://agentmods.dev/badge/plugins/lukawi/super-plumber/plugin/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/plugins/lukawi/super-plumber/plugin"><img src="https://agentmods.dev/badge/plugins/lukawi/super-plumber/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
super-plumber 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
{
"name": "super-plumber",
"description": "Super Plumber workflow orchestration plugin: design task graphs as agent-native topologies, then execute them node by node.",
"version": "1.0.0",
"author": {
"name": "lukawi",
"url": "https://www.npmjs.com/package/@lukawi/super-plumber"
},
"keywords": [
"workflow",
"topology",
"mcp",
"agents",
"skills"
],
"skills": [
{
"name": "plumber-design",
"invocation": "model-invoked",
"command": "plumber-design"
},
{
"name": "plumber-execute",
"invocation": "model-invoked",
"command": "plumber-execute"
},
{
"name": "plumber-join",
"invocation": "model-invoked",
"command": "plumber-join"
},
{
"name": "plumber",
"invocation": "model-invoked",
"command": "plumber"
},
{
"name": "sp-grilling",
"invocation": "model-invoked",
"command": null
},
{
"name": "plumber-tdd",
"invocation": "model-invoked",
"command": null
},
{
"name": "plumber-review",
"invocation": "model-invoked",
"command": null
}
]
}
What it installs
The manifest is a name and a version. 4 commands, 1 MCP server travel with it, and installing the plugin installs all of them — 145 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 Changed 08d25f3bef62
- 1mo ago Changed · +37 lines 4d9e50171fc5
- 1mo ago Changed · -26 lines cb0e56ecd5cf
- 1mo ago Changed · +5 lines e879b55a1f33
- 1mo ago First seen · 38 lines scan A be1390d1cf6d
super-plumber is a plugin published in the GitHub repository LUKAWI/super-plumber (3 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
themes-example
themes-example. An open-source AI agent that brings the power of Gemini directly into your terminal.
knowledge-work-plugins marketplace
Plugin marketplace listing 123 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
superpowers
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques.