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.
git clone --depth 1 https://github.com/hjqcan/GoodMemoryWrote 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/hjqcan/goodmemory/trace)<a href="https://agentmods.dev/commands/hjqcan/goodmemory/trace"><img src="https://agentmods.dev/badge/commands/hjqcan/goodmemory/trace/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.
<a href="https://agentmods.dev/commands/hjqcan/goodmemory/trace"><img src="https://agentmods.dev/badge/commands/hjqcan/goodmemory/trace.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00009 | $0.00196 |
| Opus 5.5 | $0.00004 | $0.00078 |
| Sonnet 5.5 | $0.00002 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
trace 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.
What it actually says
Call mcp__goodmemory__goodmemory_trace_recall with query set to
$ARGUMENTS, retrievalProfile set to coding_agent, and cwd set to the
current project absolute path. Summarize routing, hits, scores, and suppression
reasons without presenting the trace as proof that a memory is true. If
$ARGUMENTS is empty, ask for the query to diagnose.
Omit optional arguments unless the user supplied them. Do not invent
referenceTime, timezone, or sessionId; let the server resolve its default
time and durable workspace scope. Do not run a shell command to obtain a clock
value just to fill an optional field.
If the active tool schema permits null, use it for an unknown optional value
when omission is unavailable. Never use empty strings as absence markers.
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.
- 1mo ago Changed · +7 lines a268bdca75b4
- 1mo ago First seen · 10 lines · 9 tokens per session scan A 0eb8ebf1f87f
trace is a command published in the GitHub repository hjqcan/GoodMemory (19 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 196 once invoked, about $0.0000 per session on Opus 5.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.
Other commands, from other repositories
recall
Search this machine's past AI coding sessions (deja-vu).
krimto-status
Show the current state of Krimto memory — total facts, scope breakdown, recent writes, and index health.
compass-verify
Verify the Merkle hash chain over /.claude/projects/ /memory/ and report any tampered or missing files.
tree-ring-recall
Recall durable Tree Ring Memory context before starting or resuming work.
tree-ring-update
Check for or install a verified Tree Ring Memory CLI update without changing installation scope.
tree-ring-status
Check receipt-backed Tree Ring harness readiness without claiming configuration is activation.