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/terminallylazy/tree-ring-memory-claude-plugin/tree-ring-memorynpx skills add TerminallyLazy/tree-ring-memory-claude-plugin --skill tree-ring-memorygit 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/skills/terminallylazy/tree-ring-memory-claude-plugin/tree-ring-memory)<a href="https://agentmods.dev/skills/terminallylazy/tree-ring-memory-claude-plugin/tree-ring-memory"><img src="https://agentmods.dev/badge/skills/terminallylazy/tree-ring-memory-claude-plugin/tree-ring-memory.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.00038 | $0.05093 |
| Opus 5 | $0.00019 | $0.02547 |
| Sonnet 5 | $0.00008 | $0.01019 |
| Haiku 4.5 | $0.00004 | $0.00509 |
Grade B, and why
tree-ring-memory scanned grade B with 1 finding 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 3d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
# Set and export TREE_RING_COORDINATOR_TOKEN with a history-safe, no-echo prompt This is a copy
94% identical to tree-ring-memory — 30 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.
How it starts
The opening of the file, as written. The whole thing — 526 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tree Ring Memory
Use Tree Ring Memory as a lifecycle-aware memory layer, not as a transcript dump.
Tree Ring Memory preserves meaningful agent learning like tree rings:
- fresh work stays detailed
- older learning compresses into stable rings
- important warnings remain visible as scars
- durable truths become heartwood
- speculative future work stays as seeds
- sensitive data is blocked, redacted, or kept out by default
Runtime Bootstrap And Updates
Resolve the actual project root before running Tree Ring. Never initialize a plugin cache, downloaded package directory, home directory, or arbitrary working directory by accident.
-
If
<project-root>/.tree-ring/bin/tree-ringexists, prefer that binary for this project. Otherwise checkcommand -v tree-ringand runtree-ring --version. -
Read existing
<project-root>/.tree-ring/SKILL.mdandCLI.mdwhen present. -
This package targets Tree Ring Memory CLI 0.15.0 or newer. If no compatible CLI is available and the user's request already authorizes Tree Ring setup, install the verified current release project-locally from the project root. Otherwise explain the exact operation and obtain permission before the network download or software installation. Download the official, version-pinned
v0.15.0/install.shinstaller to a temporary file, verify its SHA-256 isef0d5eb8f09cbe2e4c3abe80ee9a98a56759c89ad4ddd103d6c68314cd653ade, inspect it, and only then run:cd <project-root> sh <verified-installer-path> --project --init --release latest --no-animationDo not pipe a network response directly to a shell. The installer verifies the selected release archive against its published SHA-256 before placing the binary at
<project-root>/.tree-ring/bin/tree-ring. -
For an existing global CLI, initialize from the project root with
tree-ring --root .tree-ring init. For a project-local CLI, use.tree-ring/bin/tree-ring --root .tree-ring init. This must placememory.sqlite,AGENTS.md,SKILL.md, andCLI.mdunder that project's.tree-ring/directory. -
Verify the created paths and run the same binary with
--root .tree-ring integrations status. Initialization creates safe local guidance and bridge material; it is not receipt-backed activation proof.
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.
- 3d ago First seen · 526 lines · 38 tokens per session scan B 874f5bb44a43
tree-ring-memory is a skill published in the GitHub repository TerminallyLazy/tree-ring-memory-claude-plugin (0 stars, last pushed 9d ago), licensed MIT. It adds 38 tokens to every session and 5,093 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). It is 94% identical to tree-ring-memory, differing in 30 lines, and is treated as a copy.
Other skills, from other repositories
graph-ask
Ask any natural language question about the memory graph. You generate Cypher directly and execute it. Use when the user has a complex or ad-hoc question that the standard graph tools don't cover.
ingest-audio
Transcribe a local audio or video file using Whisper and ingest it into the memory graph. Use when the user has a local MP3, WAV, M4A, MP4, or similar audio/video file they want to add to their knowledge graph.
ingest
Ingest a file or URL into the memory graph. Handles local files (text, PDF, DOCX, XLSX, images, etc.) and URLs (web pages, YouTube, Wikipedia, RSS). Use when the user wants to add any document or web content to their knowledge graph.
graph-backup
Export the memory graph to a timestamped JSONL backup file. Use before risky operations or on demand.
graph-briefing
Generate a session briefing from the memory graph — recent changes, unresolved contradictions, relevant context for the current project. Use at the start of a session to catch up, or when switching projects.
graph-dream
Manually run the graph memory dream process to extract entities from recent conversations and ingested documents. Use when the user wants to update the graph now rather than waiting for the scheduled run.