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/peterpirog/mcp-light-memory/checkpointgit clone --depth 1 https://github.com/PeterPirog/mcp-light-memoryWhat 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.00004 | $0.00039 |
| Opus 5 | $0.00002 | $0.00019 |
| Sonnet 5 | $0.00001 | $0.00008 |
| Haiku 4.5 | $0.00000 | $0.00004 |
Grade A, and why
checkpoint 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 yesterday.
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.
What it actually says
Load internal-rag. Inspect current Git state, then run checkpoint with concise phase/completed/in-progress/blockers/next fields. Run guard afterward.
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.
- yesterday First seen · 6 lines · 4 tokens per session scan A 7a74efe67d92
checkpoint is a command published in the GitHub repository PeterPirog/mcp-light-memory (0 stars, last pushed 5d ago), licensed MIT. It adds 4 tokens to every session and 39 once invoked, about $0.0000 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-31.
Other commands, from other repositories
tree-ring-update
Check for or install a verified Tree Ring Memory CLI update without changing installation scope.
tree-ring-certify
Generate Tree Ring harness or recall-quality evidence without confusing it with the full framework release suite.
tree-ring-dox-sync
Preview and synchronize DOX-style AGENTS.md guidance as source-linked Tree Ring memory.
tree-ring-recall
Recall durable Tree Ring Memory context before starting or resuming work.
tree-ring-status
Check receipt-backed Tree Ring harness readiness without claiming configuration is activation.
wrap
Close the session cleanly. Update entity state. Capture decisions. Detect momentum shifts.