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/lx-wnk/agent-context/memory-reviewgit clone --depth 1 https://github.com/lx-wnk/Agent-ContextWrote 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/lx-wnk/agent-context/memory-review)<a href="https://agentmods.dev/commands/lx-wnk/agent-context/memory-review"><img src="https://agentmods.dev/badge/commands/lx-wnk/agent-context/memory-review.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.00013 | $0.00057 |
| Opus 5 | $0.00006 | $0.00028 |
| Sonnet 5 | $0.00003 | $0.00011 |
| Haiku 4.5 | $0.00001 | $0.00006 |
Grade A, and why
memory-review 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.
What it actually says
Read .agent-context/memory-review-prompt.md and follow it exactly to review this project's memory files. This is the manual trigger for the same review you can also schedule via /schedule.
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 · 6 lines · 13 tokens per session scan A 9f2e59d4a12d
memory-review is a command published in the GitHub repository lx-wnk/Agent-Context (7 stars, last pushed 4d ago), licensed MIT. It adds 13 tokens to every session and 57 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-31.
Other commands, from other repositories
ov
Show OpenViking memory plugin status — server, identity, last injection / recall, toggles.
weekly
Weekly memory report — facts learned, procedures, repeated mistakes prevented.
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-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.