tree-ring-status

A status-check command for Tree Ring Memory, a project memory system that stores durable agent knowledge. It checks the installed runtime and verifies whether the memory harness is genuinely active.

In plain words
What is it for?
Use it to check the Tree Ring version, inspect integration readiness, and identify the exact next step when activation is incomplete.
Why use it?
It prevents setup markers or configuration files from being mistaken for working activation. It reports the actual readiness state without changing it.

Command

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-status
Clone the repo
git clone --depth 1 https://github.com/TerminallyLazy/Tree-Ring-Memory
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 282 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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.00282
Opus 5 $0.00006 $0.00141
Sonnet 5 $0.00002 $0.00056
Haiku 4.5 $0.00001 $0.00028

Measured 2d ago against content hash 493a5b740455, 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-status 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:

plugins/tree-ring-memory/commands/tree-ring-status.md · 36 lines

What it actually says

Tree Ring Status

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 project-local or global runtime is Tree Ring Memory 0.15.0 or newer:

tree-ring --version

Bootstrap or upgrade when the user's request already authorizes it; otherwise obtain permission before downloading or changing software. Never invent a status.

Inspect receipt-backed readiness without changing it:

tree-ring integrations status --json --verbose

Report the exact harness state, capability, and next_step. A bridge, marker, generated skill, passive binding, or successful init is not activation proof. Only a fresh matching receipt from a new session's scoped recall and safe context injection can produce active.

Treat configured-awaiting-proof, active-isolated, needs-trust, needs-project-mount, needs-plugin, needs-user-review, unsupported, and failed as non-active outcomes. Do not modify global trust, manufacture a receipt, hand-author an Agent Zero capability descriptor, or replace a contested bridge while checking status.

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.

  1. 2d ago First seen · 36 lines · 12 tokens per session scan A 493a5b740455

Subscribe to this mod's changes

tree-ring-status is a command published in the GitHub repository TerminallyLazy/Tree-Ring-Memory (16 stars, last pushed 4d ago), licensed MIT. It adds 12 tokens to every session and 282 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.