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-statusgit 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-status)<a href="https://agentmods.dev/commands/terminallylazy/tree-ring-memory-claude-plugin/tree-ring-status"><img src="https://agentmods.dev/badge/commands/terminallylazy/tree-ring-memory-claude-plugin/tree-ring-status.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.00012 | $0.00282 |
| Opus 5 | $0.00006 | $0.00141 |
| Sonnet 5 | $0.00002 | $0.00056 |
| Haiku 4.5 | $0.00001 | $0.00028 |
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 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-status — 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 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.
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 · 36 lines · 12 tokens per session scan A 493a5b740455
tree-ring-status is a command published in the GitHub repository TerminallyLazy/tree-ring-memory-claude-plugin (0 stars, last pushed 9d 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. It is 100% identical to tree-ring-status, 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).