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/studiomeyer-io/studiomeyer-marketplaceWrote 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/studiomeyer-io/studiomeyer-marketplace/memory-recall-timeline)<a href="https://agentmods.dev/commands/studiomeyer-io/studiomeyer-marketplace/memory-recall-timeline"><img src="https://agentmods.dev/badge/commands/studiomeyer-io/studiomeyer-marketplace/memory-recall-timeline/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/studiomeyer-io/studiomeyer-marketplace/memory-recall-timeline"><img src="https://agentmods.dev/badge/commands/studiomeyer-io/studiomeyer-marketplace/memory-recall-timeline.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.00016 | $0.00193 |
| Opus 5 | $0.00008 | $0.00097 |
| Sonnet 5 | $0.00003 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
memory-recall-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 6d 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
Render a vertical chronological timeline of the user's recent memory activity.
- Parse
$ARGUMENTSas an integer day count. If empty or non-numeric, default to 14. - Call
nex_recall_timelinefrom thestudiomeyer-memoryMCP server withdays: <parsed>andlimit: 200. - The host renders the interactive timeline inline (in MCP Apps capable hosts) OR returns the structured JSON with learnings, decisions and sessions ordered by date. Both behaviors are correct.
- Summarize the result in two lines: total items, breakdown by type (learn / decide / session), date range covered.
- Do not invent items. If the response is empty, say so directly and suggest the user widens the day window.
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.
- 6d ago Changed 9d2d16465dc0
- 11d ago First seen · 13 lines · 16 tokens per session scan A adf665000939
memory-recall-timeline is a command published in the GitHub repository studiomeyer-io/studiomeyer-marketplace (2 stars, last pushed 6d ago), licensed MIT. It adds 16 tokens to every session and 193 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
pane
Open the Engram graph pane — make sure the machine core is running and share the URL.
save
Manually save current context as a memo to the memex vault.
status
Show memex statistics and status including projects, memos, and pending items.
digest
Digest this project into Engram — an explicit, one-time ingestion of the current working tree into typed memory nodes.
log
Command "log" from allenc84/sapience, covering /log — judgment ledger command, routing, new assessment: /log, review: /log review [domain] and resolve: /log resolve.
recall
Search the engineering memlog and inject the top matching prior lessons. Use when you suspect a recurring issue.