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/reikor-arg/inmemory/timelinegit clone --depth 1 https://github.com/Reikor-Arg/inmemoryWrote 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/reikor-arg/inmemory/timeline)<a href="https://agentmods.dev/commands/reikor-arg/inmemory/timeline"><img src="https://agentmods.dev/badge/commands/reikor-arg/inmemory/timeline.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.00011 | $0.00135 |
| Opus 5 | $0.00005 | $0.00068 |
| Sonnet 5 | $0.00002 | $0.00027 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
timeline 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
Run with Bash:
node "${CLAUDE_PLUGIN_ROOT}/hooks/recall.mjs" timeline $ARGUMENTS
Every session, newest first, grouped by ISO week with turn and file counts. Nothing here was written by a model: the one-line description of each session is the user's own first message, verbatim.
Summarise the arc for the user. If a week is missing or a session shows only an
init command, say so rather than inventing what happened.
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 · 18 lines · 0 tokens per session scan A 0df6bb2e895c
timeline is a command published in the GitHub repository Reikor-Arg/inmemory (1 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 135 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
recall-loop
Periodic memory digest — designed for use with Claude Code's /loop scheduler. Shows recent memories and pending to-dos in a compact, scannable format.
context-stats
Show context window usage, active tier, and system stats.
today
Create a morning heartbeat from repository state and update the local heartbeat log.
capture
Triage raw inbox notes into reviewed repository destinations without deleting their sources.
start
Start a session — load state files, flag staleness, and give a briefing on current priorities, deadlines, and blockers.
update
Mid-session checkpoint — append progress to today's session log and update state files if a priority shifted, without ending the session.