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 plumbkit/plumb --skill plumb-exploregit clone --depth 1 https://github.com/plumbkit/plumbWrote 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/plumbkit/plumb/plumb-explore)<a href="https://agentmods.dev/skills/plumbkit/plumb/plumb-explore"><img src="https://agentmods.dev/badge/skills/plumbkit/plumb/plumb-explore/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/plumbkit/plumb/plumb-explore"><img src="https://agentmods.dev/badge/skills/plumbkit/plumb/plumb-explore.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.00015 | $0.01358 |
| Opus 5.5 | $0.00006 | $0.00543 |
| Sonnet 5.5 | $0.00003 | $0.00272 |
| Haiku 4.5 | $0.00002 | $0.00136 |
Grade A, and why
plumb-explore 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When asked to understand, explore, or navigate a codebase that has plumb available, work down this ladder rather than reading whole files:
workspace_search → topology / LSP → search_in_files → bounded read_file
Each rung is broader and cheaper than the one below it. Start at the top and drop down only when the note under the rung applies.
Under a lean tool profile several of the tools named below are not advertised. If one of them is not offered to you, use the nearest alternative on the same rung — for rung 0's opening move that is topology_search. Rung 3 is the thinnest: both its tools are hidden under lean, so a lean client falls back to its own native search — though lean read_file still takes pattern, use_regex, and max_matches, which covers scanning a file you have already located without leaving plumb.
0. Ranked discovery — start here
Before reaching for a shell grep, find, or ls, start on this ladder. Those three moves are what it replaces: a conceptual question belongs on this rung, grep belongs on rung 3's search_in_files, and find/ls belong on find_files. Prefer them whenever they are offered to you — they are workspace-bounded, .gitignore-aware, and bounded in output, none of which a shell scan is.
One query across every indexed corpus at once — code symbols, doc sections, and project memories — with each hit labelled by corpus, score, and why it matched.
workspace_search— the opening move for a conceptual question ("where is daemon locking handled?").
Drop down once a hit gives you a symbol or file worth following — or straight away when you already know the name. This rung is approximate by design and never proof of absence.
Starting a task? Make one call: context_for_task with the files and symbols you know as files / symbols, or with only the task in task (add intent: "change" when you will edit). It returns a bounded pack grown from those seeds — what resolved, what did not (with labelled candidates, never a guess), the gaps it cannot cover, and the exact next calls — so you need not walk the rungs below by hand. Given only prose, it proposes up to 3 seeds and labels each with how it was found (named in the task, or found by search on the words it matched); check them, and pass your own files / symbols when they are off.
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.
- 4d ago Changed 726454703003
- 7d ago Changed · +2 lines 44f48dfdae2f
- 19d ago Changed 7ba06d3a1f0c
- 1mo ago Changed 7130a6c0e45a
- 1mo ago First seen · 63 lines · 15 tokens per session scan A a3b6de75eb97
plumb-explore is a skill published in the GitHub repository plumbkit/plumb (4 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 1,358 once invoked, about $0.0001 per session on Opus 5.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
yaml
Validate and understand schema-backed YAML (Kubernetes, Flux, and JSON-Schema configs) with the yayamlls language server. Use when editing or reviewing .yaml/.yml files, diagnosing schema validation errors, configuring .yayamlls.yaml, suppressing a diagnostic, or working with Flux HelmRelease / Kustomization rendering.
use-modern-go
Use the Modern Go Guidelines CLI whenever writing, modifying, fixing, or refactoring Go code. Apply its version-specific guidance to generated changes.
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
go-127
What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…
bubbletea-testing
Use this skill whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go. Triggers include any mention of testing Bubble Tea models, teatest, golden file testing for TUIs, testing tea.Cmd or tea.Msg, snapshot testing terminal output, or writing tests for any Go CLI/TUI that uses the Elm…
design-review
Deep design review of Go codebase — naming, structure, consistency, interfaces, error handling. Scores each dimension and provides actionable fixes.