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 agentmods add skills/plumbkit/plumb/plumb-gitnpx skills add plumbkit/plumb --skill plumb-gitgit clone --depth 1 https://github.com/plumbkit/plumbWhat 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 | $0.00056 | $0.01676 |
| Opus 5 | $0.00028 | $0.00838 |
| Sonnet 5 | $0.00011 | $0.00335 |
| Haiku 4.5 | $0.00006 | $0.00168 |
Grade A, and why
plumb-git 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 2d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plumb's git tool is a policy-gated wrapper, not a shell. The subcommand leads the argv, nothing is interpolated by a shell, and eight global flags that could re-target the repository or inject config are refused wherever they appear in args: -c, -C, --exec-path, --git-dir, --work-tree, --namespace, --upload-pack, --receive-pack. The one exception is switch, where -c / -C mean create-branch rather than anything global: they are rewritten to --create / --force-create before the denylist runs, and the response says so. Prefer this tool over shelling out — the shell path bypasses the policy and plumb's per-repository git lock.
Under a lean tool profile file_status and minimal_diff_review are not advertised; set [tools] profile = "full" in .plumb/config.toml to see them.
The four tiers
| Tier | Subcommands | Gate |
|---|---|---|
| read | status, log, diff, show, blame, shortlog, check-ignore |
always allowed |
| write | add, commit, mv |
[git] allow_writes |
| destructive | reset, clean, rebase, revert, cherry-pick |
[git] allow_destructive and a confirmation |
| network | push, fetch, pull |
[git] allow_push and a confirmation |
rm is refused at every tier: delete the file with delete_file, then stage the deletion with add.
Six subcommands are classified by their arguments, biased towards the safer-to-deny higher tier — so the same subcommand can land in different tiers on different calls:
checkout -b/-B(branch creation) is write; every othercheckoutis destructive, since it can discard the working tree or detach HEAD. Preferswitchfor a safe branch change.switchis write, butswitch -f/--force/--discard-changesis destructive.restore: with--staged(the index only) it is write; with--worktree, or with no flag at all, it is destructive.branch:--list/-l/-a/-r/-v/--show-current/--contains/--merged, and a barebranch, are read; creating,-m/-M/--move/--copyare write;-d/-D/--deleteis destructive.tag:-l/--list/-n/--contains/--merged, and a baretag, are read; creating is write;-d/--deleteis destructive.stash:list/showare read; a barestashpluspush/save/pop/apply/create/storeare write;drop/clearare destructive; any other sub-subcommand is refused with the permitted list.
session_start prints the live policy — read it there rather than discovering a tier by being refused.
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.
- 2d ago First seen · 80 lines · 56 tokens per session scan A 6c895dce0474
plumb-git is a skill published in the GitHub repository plumbkit/plumb (4 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 1,676 once invoked, about $0.0003 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
nim-mcp-tools
Use for Nim symbol navigation, diagnostics, and type resolution. MANDATORY: Use specialized MCP tools (nimFindSymbols, nimFindReferences, nimListSymbols, nimCheckFile, nimCheckProject, nimFindTypeDefinition) first; fall back to grep only on error or user confirmation.
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.
lsp-config
This skill should be used when the user asks about "LSP configuration", "language server setup", "adding LSP to Claude Code", "mason config import", "lspconfig migration", "lspctl plugin", or discusses Claude Code LSP integration and troubleshooting.
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern.
fleet-manager
Use when managing, triaging, restarting, escalating, or summarizing Codewhale Pod runs and workers.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.