tree-ring-capture

tree-ring-capture is a command for Claude Code from TerminallyLazy/tree-ring-memory-claude-plugin. It costs 13 tokens per session (921 once invoked), scanned A, a copy of tree-ring-capture, MIT.

A command for saving one durable, validated lesson, decision, warning, or preference in Tree Ring Memory, rather than storing a conversation transcript.

In plain words
What is it for?
Use it to record project- or agent-scoped lessons with the required workflow, session, operation, and source details when coordinated mode is used.
Why use it?
It preserves useful information for later work while excluding secrets, raw reasoning, transcripts, and unverified claims.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the tree-ring-memory plugin — 1 skill, 7 commands shipped together

Good fit Use it to record project- or agent-scoped lessons with the required workflow, session, operation, and source details when coordinated mode is used.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/terminallylazy/tree-ring-memory-claude-plugin/tree-ring-capture
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.

Clone the repo
git clone --depth 1 https://github.com/TerminallyLazy/tree-ring-memory-claude-plugin

Made for: Claude Code.

Or install tree-ring-memory, the plugin that ships this one along with the rest of its 1 skill, 7 commands.

Wrote 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.

agentmods badge for tree-ring-capture

README.md
[![agentmods](https://agentmods.dev/badge/commands/terminallylazy/tree-ring-memory-claude-plugin/tree-ring-capture/github.svg)](https://agentmods.dev/commands/terminallylazy/tree-ring-memory-claude-plugin/tree-ring-capture)
Your own site
<a href="https://agentmods.dev/commands/terminallylazy/tree-ring-memory-claude-plugin/tree-ring-capture"><img src="https://agentmods.dev/badge/commands/terminallylazy/tree-ring-memory-claude-plugin/tree-ring-capture/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.

agentmods 80×15 button for tree-ring-capture

Your own site · 80×15
<a href="https://agentmods.dev/commands/terminallylazy/tree-ring-memory-claude-plugin/tree-ring-capture"><img src="https://agentmods.dev/badge/commands/terminallylazy/tree-ring-memory-claude-plugin/tree-ring-capture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 921 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 89% copy Near-identical to another mod 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.1 $0.00013 $0.00921
Opus 5.5 $0.00005 $0.00368
Sonnet 5.5 $0.00003 $0.00184
Haiku 4.5 $0.00001 $0.00092

Measured 1mo ago against content hash a5c746323caa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

tree-ring-capture 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.

Origin

This is a copy

89% identical to tree-ring-capture — 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.

commands/tree-ring-capture.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Tree Ring Capture

Capture only durable, useful memory. Do not store transcripts, secrets, credentials, raw chain-of-thought, or unverified claims as truth.

Lifecycle Stop Checkpoint

Stop and SubagentStop hooks enforce one agent-mediated checkpoint. The hook never inspects or persists transcript_path, last_assistant_message, prompts, or transcript content. Evaluate the grounded work already in the active agent's context. If there is no durable, normal-sensitivity candidate, do not write a memory.

For each qualifying candidate, use the exact identity-bound template returned by the lifecycle handler. Its strict shape is:

tree-ring --root .tree-ring capture "<concise summary>" \
  --event-type <preference|decision|lesson|warning|correction|seed> \
  --ring <cambium|scar|seed> \
  --project <project> \
  --agent-profile <profile> \
  --workflow-id <workflow> \
  --session-id <session> \
  --operation-id auto-<checkpoint>-<1..3> \
  --source-ref agent-checkpoint:<checkpoint> \
  [--tag <tag>]

Do not invent or edit the supplied identity, checkpoint, operation, or source values. Strict capture fixes scope=agent, requires identity and provenance, adds the automatic-capture tag, and accepts normal sensitivity only. Use no more than three candidates in the single checkpoint. Never replace this with a raw transcript summary, remember, evidence, or an import.

Use cambium for preferences, decisions, lessons, and corrections; scar for warnings; and seed for future work. A candidate still must be durable and grounded regardless of its ring.

The manual command flow below remains available for an explicit user-directed capture outside a lifecycle checkpoint.

Read project-local .tree-ring/SKILL.md and .tree-ring/CLI.md first when present. Follow the skill's Runtime Bootstrap And Updates procedure and confirm the selected project-local or global 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 a stored memory.

Read the full file on GitHub · 102 lines

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. 1mo ago Changed · +37 lines a5c746323caa
  2. 1mo ago First seen · 65 lines · 13 tokens per session scan A a999f3c6a1d0

Subscribe to this mod's changes

tree-ring-capture is a command published in the GitHub repository TerminallyLazy/tree-ring-memory-claude-plugin (0 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 921 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to tree-ring-capture, differing in 0 lines, and is treated as a copy.