What is tree-ring-dox-sync?

A command for previewing and saving guidance from AGENTS.md files into Tree Ring memory. It keeps links back to the original instructions so the source remains authoritative.

Use it to inspect and synchronize project guidance from the project root to the current working directory. It can preview changes without writing them, then save an approved synchronization.

It helps review proposed summaries before they are saved and avoids copying secrets, contracts, or unnecessary text into memory.

tree-ring-dox-sync — Command by TerminallyLazy

Install

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.

agentmods

npx agentmods add commands/terminallylazy/tree-ring-memory/tree-ring-dox-sync

Clone the repo

git clone --depth 1 https://github.com/TerminallyLazy/Tree-Ring-Memory

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 372 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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

Measured 2d ago against content hash 501db5f448f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

tree-ring-dox-sync — 100% identical, 0 lines differ

plugins/tree-ring-memory/commands/tree-ring-dox-sync.md · 37 lines

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.md chain 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.md and .tree-ring/CLI.md when 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 requires TREE_RING_COORDINATOR_TOKEN in 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.

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.

2d ago First seen · 37 lines · 16 tokens per session scan A 501db5f448f3

Subscribe to this mod's changes

tree-ring-dox-sync is a command published in the GitHub repository TerminallyLazy/Tree-Ring-Memory (16 stars, last pushed 4d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Memory and context agent-memory ai-agents cli developer-tools dox local-first

tree-ring-dox-sync

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

What it actually says

Tree Ring DOX Sync

What this file has done since we first saw it

Other commands, from other repositories

wrap

focus

reconcile

brain

decide

graph