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/atazifor/engineering-memlog/recallgit clone --depth 1 https://github.com/atazifor/engineering-memlogWrote 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/atazifor/engineering-memlog/recall)<a href="https://agentmods.dev/commands/atazifor/engineering-memlog/recall"><img src="https://agentmods.dev/badge/commands/atazifor/engineering-memlog/recall.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.00021 | $0.00367 |
| Opus 5 | $0.00010 | $0.00183 |
| Sonnet 5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
recall 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 3d 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
You will run a memlog search for the query and read the JSONL output back to the user.
Steps:
- Run the memlog search command with the user's query:
~/engineering-memory/bin/memlog search "$ARGUMENTS" --json --limit 10
If $ARGUMENTS is empty, instead run:
~/engineering-memlog/scripts/memlog-context | ~/engineering-memlog/scripts/memlog-shortlist --file ~/engineering-memory/data/entries.jsonl --limit 10
-
Parse each JSONL line. For every hit, show the user a compact summary:
timestamp(date only, YYYY-MM-DD)title- one-line excerpt of
problem(first ~120 chars) tags(joined with commas)confidence
-
After the list, ask the user which entry (if any) looks relevant to the current task. If they confirm one, retrieve and read its full
preventionfield aloud — that's the rule they should apply. -
If
memlogis not installed or the data file is missing, report that clearly and link to the install instructions in the engineering-memlog README.
Important:
- Don't dump raw JSON unless the user asks — present a readable summary.
- Don't paraphrase the
preventionrule when reading it back; quote it verbatim. Paraphrasing loses precision. - If zero hits, say so and suggest alternate queries (e.g. broader keywords from the user's question).
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.
- 3d ago First seen · 38 lines · 21 tokens per session scan A 85576fd45da3
recall is a command published in the GitHub repository atazifor/engineering-memlog (1 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 367 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
tree-ring-capture
Capture a concise validated lesson decision warning or preference in Tree Ring Memory.
tree-ring-audit
Audit consolidate or forget stale sensitive or superseded Tree Ring Memory entries.
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-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.