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 commands/terminallylazy/tree-ring-memory-claude-plugin/tree-ring-recallgit clone --depth 1 https://github.com/TerminallyLazy/tree-ring-memory-claude-pluginWrote 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-claude-plugin/tree-ring-recall)<a href="https://agentmods.dev/commands/terminallylazy/tree-ring-memory-claude-plugin/tree-ring-recall"><img src="https://agentmods.dev/badge/commands/terminallylazy/tree-ring-memory-claude-plugin/tree-ring-recall.svg" alt="Measured on agentmods" 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 | $0.00012 | $0.00417 |
| Opus 5 | $0.00006 | $0.00209 |
| Sonnet 5 | $0.00002 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
tree-ring-recall 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 4d 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.
This is a copy
100% identical to tree-ring-recall — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Tree Ring Recall
Recall useful project memory before acting on context-dependent work.
-
Check for project-local guidance first:
test -f .tree-ring/SKILL.md && sed -n '1,520p' .tree-ring/SKILL.md test -f .tree-ring/CLI.md && sed -n '1,520p' .tree-ring/CLI.mdFollow the skill's Runtime Bootstrap And Updates procedure and confirm the selected binary reports 0.15.0 or newer. Bootstrap or upgrade when the user's request already authorizes it; otherwise obtain permission before downloading or changing software. Never fabricate recall.
-
Use the user's argument as the focused recall query when present:
tree-ring recall "$ARGUMENTS" -
If no argument is provided, choose a narrow query from the current task and include project scope when known.
-
In a fan-out worker, filter recall with its agent profile plus the shared workflow and current session. At coordinator fan-in, omit only the agent-profile filter deliberately so all worker results remain visible:
env -u TREE_RING_AGENT_PROFILE tree-ring recall "$ARGUMENTS" \ --workflow-id "$TREE_RING_WORKFLOW_ID" \ --session-id "$TREE_RING_SESSION_ID" \ --scope agent -
Treat recall as context, not authority. Prefer source-linked, high-confidence, non-superseded entries and verify drift-prone facts before relying on them.
Identity and scope partition and route local memory; they are not read ACLs. The supported shared-root boundary is cooperative processes on one host and a local filesystem, not cross-host or network-filesystem coordination.
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.
- 4d ago First seen · 50 lines · 12 tokens per session scan A 61b94d6f5689
tree-ring-recall is a command published in the GitHub repository TerminallyLazy/tree-ring-memory-claude-plugin (0 stars, last pushed 10d ago), licensed MIT. It adds 12 tokens to every session and 417 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to tree-ring-recall, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
recall
Search the engineering memlog and inject the top matching prior lessons. Use when you suspect a recurring issue.
weekly
Weekly memory report — facts learned, procedures, repeated mistakes prevented.
evolve-lite-adapt-memory
Mirror a just-saved native memory into the shared evolve store so it becomes shareable and auditable.
reclaim-knowledge
Organize scattered professional material into a domain-based second-brain architecture. Maps existing sources (Canva, Drive, local folders, Notion, screenshots) to functional domains. Non-technical-friendly — produces folder structure + drag-and-drop instructions, not CLI commands.
distill-insights
Distill captures from a window (week / month / quarter) into named frameworks. Applies ≥3-occurrence threshold. Cross-references against Genius Profile. Produces a distillate document and optional Profile evolution proposals.
orchestrate-brain
Weekly 30-minute second-brain review ritual. Orchestrates inbox clear, lightweight distillation, vault maintenance, cross-reference pass, and next-week capture focus. The compounding rhythm that keeps the system alive.