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-memorygit 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-memory)<a href="https://agentmods.dev/skills/plumbkit/plumb/plumb-memory"><img src="https://agentmods.dev/badge/skills/plumbkit/plumb/plumb-memory/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-memory"><img src="https://agentmods.dev/badge/skills/plumbkit/plumb/plumb-memory.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.00046 | $0.00917 |
| Opus 5.5 | $0.00018 | $0.00367 |
| Sonnet 5.5 | $0.00009 | $0.00183 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
plumb-memory 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 1mo 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plumb keeps per-workspace memories as markdown under <workspace>/.plumb/memories/, indexed for ranked search. They are for knowledge that outlives one session and has no better home in the code — not a scratchpad, and not a substitute for a comment or a doc.
Under a lean tool profile only search_memories is advertised; set [tools] profile = "full" in .plumb/config.toml to get the rest of this lane.
1. Look before you derive
Re-deriving a constraint someone already recorded is the failure this lane exists to stop.
search_memories(pattern="rate limiter")
relevant_memories(path="internal/tools/edit_file.go")
search_memories is ranked FTS5 while the index is fresh and falls back to substring grep otherwise. relevant_memories takes the other route in — the memories whose stored paths globs match a file you are about to touch, which is the one you want immediately before an edit.
session_start already surfaces the top memories and any last-session summary, so re-listing them is usually wasted; reach for these when you need something it did not show.
2. Pick the search mode deliberately
search_memories(pattern="essio", mode="grep")
mode is auto (the default), fts, or grep. FTS5 tokenises whole words, so a substring inside an identifier — essio within UserSession — never matches it. Auto notices an empty FTS result and greps; a literal fts keeps the empty answer. Setting case_sensitive to true also forces grep, because FTS5 is case-insensitive; leaving it unset keeps the default smart-case behaviour. use_regex forces grep too.
3. Read the one you want, whole
list_memories()
read_memory(name="topology-resync-pacing")
read_memory prints a provenance footer for a memory that is not user-authored. Weigh it: confidence is one of user, generated, imported, or inferred, and only user means a person wrote it deliberately. generated covers both the daemon's rule-based idle summaries (named episodic-*) and anything an agent handed over with share_findings (named finding-*) — a name prefix, not a tier of its own. Ranking and hint injection already prefer user; your reading should too.
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.
- 1mo ago First seen · 55 lines · 46 tokens per session scan A fadf3f9266c8
plumb-memory is a skill published in the GitHub repository plumbkit/plumb (4 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 917 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
memory-index
Index a folder's contents into the MemPalace semantic memory for search and retrieval. Use this skill whenever the user asks to "index a folder", "index a directory", "index memory", "mine a project into memory", "make a folder searchable", "embed a folder", "ingest code into the palace", or "index this directory for…
memory-mine
Mine project files or conversations into the MemPalace memory system. Indexes source code and conversation history as searchable palace drawers with semantic embeddings and room assignment.
memory-status
Show MemPalace memory system status — drawer counts, wings, rooms, knowledge graph stats, and embedding model state.
write-terva-lore
Author terva lore. Lore is context that a person authors in files. terva injects it only when it is keyword-relevant, or always-on. Use to create/add/write lore, "world info", a lorebook entry, keyed background, or a book of facts for a character.
handoff
Compact the current session into a handoff document. A fresh session or another agent can pick it up with no need to re-derive context. Use when asked to hand off, hand over, wrap up for another session or agent, or park work mid-stream.
retrospective
Distill the reusable lessons of this session into the durable homes that shape future sessions. The lessons are corrections, conventions you discovered, and traps you hit. The homes are the project or global AGENTS.md, a project skill, and memory when available. Use when asked for a retro, to capture or remember…