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-chatgit 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-chat)<a href="https://agentmods.dev/skills/plumbkit/plumb/plumb-chat"><img src="https://agentmods.dev/badge/skills/plumbkit/plumb/plumb-chat/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-chat"><img src="https://agentmods.dev/badge/skills/plumbkit/plumb/plumb-chat.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.00049 | $0.02088 |
| Opus 5.5 | $0.00020 | $0.00835 |
| Sonnet 5.5 | $0.00010 | $0.00418 |
| Haiku 4.5 | $0.00005 | $0.00209 |
Grade A, and why
plumb-chat 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 7d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plumb's mailbox is two tools: leave_note sends, check_messages receives. It is for coordinating with a session working the same project right now — a claim on files you are about to touch, an answer only that agent has. Every message is agent-authored, secret-scrubbed before storage, and advisory: nothing sent here blocks anyone's write. Gated on [collab] mailbox, on by default and same-workspace only. Unread messages expire after [collab] note_ttl_minutes (which follows intent_ttl_minutes until set), so an unread note does not sit forever; a workspace may also keep delivered notes forever as a transcript ([collab] keep_delivered_notes) — the read flag itself is then the permanence trigger.
Under a lean tool profile none of these tools is advertised (they stay callable by name); set [tools] profile = "full" in .plumb/config.toml to see them.
0. Be addressable: identify yourself first
session_start(session_id="<your stable per-agent id>")
Mail is addressed by session NAME, and the wake path and plumb mail --external-id are addressed by the conversation id you pass as session_id. Pass the same stable id on every session_start — the client's conversation id for a main thread, <conversation>/<agent> for a subagent. On Claude Code the identity hook (plumb hooks install claude-code) fills it on every plumb call. A session that never passes one still has a name, but a client restart starts a new identity and mail addressed to the old one does not follow; and on a connection several agents share, a state-changing call that carries no per-call identity is refused. session_id identifies only the session_start call itself; the hook (or a per-call _meta identity) is what identifies every later call.
1. Address a live session, or the next one to attach
workspace_sessions()
leave_note(to="swift-falcon", body="rewriting the rate limiter — hold off on internal/tools/ratelimit")
to is a peer session's display NAME, which workspace_sessions lists alongside how long since each session's last tool call. A name is unique among LIVE sessions — plumb refuses to register or rename onto a name another live session holds, because the name is the address — but an ended session does not reserve it, so the same name can later belong to someone else.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago Changed 80e407f00709
- 19d ago Changed 77476ccf6081
- 1mo ago Changed · +7 lines 2fe250d6f3c0
- 1mo ago Changed · +6 lines ebe836cb1694
- 1mo ago Changed 7075e014365b
- 1mo ago First seen · 73 lines · 49 tokens per session scan A 5a9b7fd82718
plumb-chat is a skill published in the GitHub repository plumbkit/plumb (4 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 2,088 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
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.