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-dox-syncgit 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-dox-sync)<a href="https://agentmods.dev/commands/terminallylazy/tree-ring-memory-claude-plugin/tree-ring-dox-sync"><img src="https://agentmods.dev/badge/commands/terminallylazy/tree-ring-memory-claude-plugin/tree-ring-dox-sync.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.00016 | $0.00372 |
| Opus 5 | $0.00008 | $0.00186 |
| Sonnet 5 | $0.00003 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
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 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-dox-sync — 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 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.
-
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.
- 4d 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-claude-plugin (0 stars, last pushed 9d ago), licensed MIT. It adds 16 tokens to every session and 372 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-dox-sync, 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.
evolve-lite-adapt-memory
Mirror a just-saved native memory into the shared evolve store so it becomes shareable and auditable.
status
Show memex statistics and status including projects, memos, and pending items.
jarvis-setup
Launch the local setup page to configure the Jarvis memory hub.
promote
Move .memory/ artifacts to permanent knowledge locations.
tour
Tour this project's memory — what's captured, where it lives, how to recall it (core-memory-kit).