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-testinggit 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-testing)<a href="https://agentmods.dev/skills/plumbkit/plumb/plumb-testing"><img src="https://agentmods.dev/badge/skills/plumbkit/plumb/plumb-testing/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-testing"><img src="https://agentmods.dev/badge/skills/plumbkit/plumb/plumb-testing.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.00040 | $0.01282 |
| Opus 5.5 | $0.00016 | $0.00513 |
| Sonnet 5.5 | $0.00008 | $0.00256 |
| Haiku 4.5 | $0.00004 | $0.00128 |
Grade A, and why
plumb-testing 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 18d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
After changing code in a codebase that has plumb available, verify the change before calling it done: ask which tests it touches, run those, and confirm the code still compiles — rather than guessing, or paying for the whole suite every time.
1. Ask which tests the change affects
topology_affected traverses inward dependency edges from what you changed and adds the tests co-located with the affected files:
topology_affected(files=["internal/tools/edit_file.go"])
topology_affected(symbols=["applyEdits"])
It is biased toward recall — a missed test is worse than an extra one — so every result carries a confidence and the reason it was flagged. Read those labels; they decide the last section.
2. Run what it named
run_task runs the project's stored [tasks.<lang>] command with no shell and bounded output:
run_task(slot="test") # the stored test command, whole
run_task(slot="verify") # build, then test
slot is build / lint / test / e2e / verify. target fills a {target} placeholder with one shell-safe argument, and the shipped go, python and rust test defaults now carry a defaulted one (go test {verbose:-v} {run:-run} {target:./...}, pytest {verbose:-v} {run:-k} {target:}, cargo test {target:} {run:--}), so scoping works on an unmodified install and a bare run_task(slot="test") still runs everything. To run one test or a pattern pass run (run_task(slot="test", target="./internal/tools", run="TestA|TestB")), and verbose=true to see which tests were skipped; mutation_test's test_run scopes each mutant the same way. npm test, swift test and zig build test have no placeholder, because those runners scope through flags whose spelling depends on the project — a target passed to a command without a placeholder is refused.
When the command takes a positional path, topology_affected hands you the target already shaped for it, relative to [tasks.<lang>].working_dir, so the two compose directly:
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.
- 18d ago Changed 8fec9861c1cd
- 1mo ago Changed · +6 lines 6f9249dfa509
- 1mo ago First seen · 50 lines · 40 tokens per session scan A 5756250ce530
plumb-testing is a skill published in the GitHub repository plumbkit/plumb (4 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,282 once invoked, about $0.0002 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
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…
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.
code-review-pi
Review code for quality, run linters, check test coverage, fix issues, and enforce gates. Save the final report to ./specs/issues/003-code-review-pi/PROMPT.md. Use before committing changes.