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.
git clone --depth 1 https://github.com/TerminallyLazy/Tree-Ring-MemoryWrote 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/commands/terminallylazy/tree-ring-memory/tree-ring-update)<a href="https://agentmods.dev/commands/terminallylazy/tree-ring-memory/tree-ring-update"><img src="https://agentmods.dev/badge/commands/terminallylazy/tree-ring-memory/tree-ring-update/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/commands/terminallylazy/tree-ring-memory/tree-ring-update"><img src="https://agentmods.dev/badge/commands/terminallylazy/tree-ring-memory/tree-ring-update.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.00412 |
| Opus 5.5 | $0.00006 | $0.00165 |
| Sonnet 5.5 | $0.00003 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
tree-ring-update 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- tree-ring-update — 100% identical, 0 lines differ
What it actually says
Tree Ring Update
Resolve the real project root and read project-local .tree-ring/SKILL.md and
.tree-ring/CLI.md when present. Prefer .tree-ring/bin/tree-ring for that
project when it exists; otherwise resolve the active global binary with
command -v tree-ring. Use which -a tree-ring to detect older shadowing
copies.
For a read-only release check, run the selected binary:
tree-ring update --check
If the user asked only to check, report the installed version, available
version, executable path, and install method without changing files. If the
user already authorized an update, run tree-ring update; otherwise obtain
permission immediately before the update. The updater must preserve the active
project-local, direct-prefix, or Homebrew scope and verify official release
assets. Never install a second copy merely to bypass an older active binary.
CLIs older than 0.15.0 lack the update command. Upgrade with the same manager or
prefix: brew upgrade tree-ring for Homebrew, the official installer with
--project --release latest for an existing project-local binary, or
--install-dir <existing-prefix> --release latest for another direct install.
Do not change global scope or edit shell startup files without separate user
authorization.
After updating, verify the selected binary with --version, return to the
actual project root, and run:
tree-ring --root .tree-ring init
tree-ring --root .tree-ring integrations status --verbose
Use .tree-ring/bin/tree-ring for both commands when the project has a local
binary. Confirm the files remain under the intended project's .tree-ring/.
Initialization refreshes managed guidance but does not prove harness activation.
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 · 46 lines · 15 tokens per session scan A 132e1dc17dfe
tree-ring-update is a command published in the GitHub repository TerminallyLazy/Tree-Ring-Memory (20 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 412 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-30.
Other commands, from other repositories
memorywhale-check
Explicitly check the reviewed MemoryWhale MCP connection; this does not enable capture or write memory.
slm-remember
Capture durable facts, decisions, constraints, and gotchas into SuperLocalMemory. Use when the user says "remember that", "save this decision", "note this constraint", or when a session produces a conclusion worth persisting across sessions. Always recall first to avoid duplicates.
slm-status
Health and optimization stats for SuperLocalMemory — call slmoptimizestats() for live compression and cache counters (compressruns, tokenssavedcompress, cacheproxyhits, cacheproxymisses, cachekvhits, cachekvmisses); run slm status [--json] for system state (mode, profile, DB size, fact/entity/edge counts) and slm…
slm-bot-memory
Cross-bot memory on a shared computer (Grok Bot, Cursor plugin, any host where several agents share one machine). Explains agentid attribution vs. profile/scope access, how to namespace by agentid + profile + scope, and what must never be written to memory. Read this before the first remember/recall on a new…
slm-getting-started-bot
First-session orientation for SuperLocalMemory on a headless bot host (Grok Bot, or any Cursor-format plugin install with no hooks, no dashboard, and no interactive setup wizard). What is different here vs. Claude Code/Codex, which 19 tools are actually available, and the first three calls to make.
slm-web-access
Set up and troubleshoot SuperLocalMemory Web access, the optional link that lets web apps (ChatGPT, Claude on the web, Muse, Composio, other remote MCP clients) use the memory on this computer. Covers turning it on from the dashboard, adding and removing apps, read/save/session permissions, the second yes for bot…