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-dox-sync)<a href="https://agentmods.dev/commands/terminallylazy/tree-ring-memory/tree-ring-dox-sync"><img src="https://agentmods.dev/badge/commands/terminallylazy/tree-ring-memory/tree-ring-dox-sync/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-dox-sync"><img src="https://agentmods.dev/badge/commands/terminallylazy/tree-ring-memory/tree-ring-dox-sync.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.00016 | $0.00453 |
| Opus 5.5 | $0.00006 | $0.00181 |
| Sonnet 5.5 | $0.00003 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
tree-ring-dox-sync 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-dox-sync — 100% identical, 0 lines differ
What it actually says
Tree Ring DOX Sync
Use the argument as the DOX source root or single AGENTS.md path. Default to
the current project root when no argument is supplied.
-
Read the applicable
AGENTS.mdchain from the project root to the working directory. Current source contracts are authoritative; a memory summary never overrides them. -
Read project-local
.tree-ring/SKILL.mdand.tree-ring/CLI.mdwhen present, then follow 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 invent adapter results. -
Preview without writing:
tree-ring dox sync --source-root "${ARGUMENTS:-.}" --dry-run -
Inspect the proposed summaries and source references. Reject raw contract copies, secrets, low-value duplication, or output that weakens a child contract.
-
Before any DOX write, run the selected binary with
--versionand require Tree Ring CLI 0.15.11 or newer. Older runtimes may preview, but must not persist DOX summaries: they lack source-root collision checks. Upgrade through the existing installation scope when authorized, then rerun and review the preview with the updated binary. -
Persist only when the user requested synchronization and the preview is concise and source-linked. Run the same command without
--dry-run. In a Coordinated store, persistence requiresTREE_RING_COORDINATOR_TOKENin the authorized coordinator process; dry-run discovery does not.
The adapter must not rewrite root or child AGENTS.md files. Re-read the live
contract chain before editing files and repeat the dry run after contract
changes.
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 Changed · +5 lines d85ed06d0a91
- 1mo ago First seen · 37 lines · 16 tokens per session scan A 501db5f448f3
tree-ring-dox-sync is a command published in the GitHub repository TerminallyLazy/Tree-Ring-Memory (20 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 453 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-session
Manage SuperLocalMemory session lifecycle — call sessioninit once at the start of every fresh session to load relevant project context and get a sessionid; call closesession when work is meaningfully complete to commit temporal summaries. Correct lifecycle hygiene is what makes SLM's learning loop work.
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.