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.
npx skills add akshatnerella/plumber --skill plumber-diagnosegit clone --depth 1 https://github.com/akshatnerella/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/akshatnerella/plumber/plumber-diagnose)<a href="https://agentmods.dev/skills/akshatnerella/plumber/plumber-diagnose"><img src="https://agentmods.dev/badge/skills/akshatnerella/plumber/plumber-diagnose/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/skills/akshatnerella/plumber/plumber-diagnose"><img src="https://agentmods.dev/badge/skills/akshatnerella/plumber/plumber-diagnose.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.00016 | $0.00139 |
| Opus 5 | $0.00008 | $0.00069 |
| Sonnet 5 | $0.00003 | $0.00028 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
plumber-diagnose 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 10d 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
Run the plumber diagnostic explicitly before writing any code. Show your work.
Format
Root cause: [what is actually broken, not the symptom]
Design flaw? [yes/no — if yes, what is wrong structurally]
Patch or redesign? [decision + one-line reason]
What to delete: [anything unnecessary]
Solution: [the genuinely simple fix]
Do not write code until the diagnosis is shown. One-shot diagnostic, then implement.
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.
- 10d ago First seen · 21 lines · 16 tokens per session scan A 600b62a60351
plumber-diagnose is a skill published in the GitHub repository akshatnerella/plumber (8 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 139 once invoked, about $0.0001 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.
Other skills, from other repositories
debugger
Systematic debugging method: 5-step root-cause analysis (capture, isolate, hypothesize, investigate, fix & verify) plus common bug-pattern reference. Use when errors, exceptions, test failures, or unexpected behavior appear. Loaded automatically by the debugger agent.
mcp-check
Validate MCP configuration and suggest improvements. Use when MCP servers fail to load, after editing .mcp.json, or when the user runs /mcp-check.
autonomous-bug-fix
Reproduces, diagnoses, fixes, and verifies bugs unaided.
debugging
Systematic root-cause investigation for hard bugs.
project-health-check
Audit project health across 7 dimensions (documentation, test coverage, security, code quality, dependencies, database, build/deploy) producing a scored report with prioritized fixes. Use for periodic checkups, before releases, or when the user runs /project-health-check.
doctor
Diagnose Cladding runtime health — Claude Code hook liveness and version, CI package pinning, lifecycle governance, and sentinel-miss frequency by phase × cause × fallback. Use when hooks may be silent, CI may float across Cladding releases, scan or run results look thinner than expected, or before tuning the host…