Memory recall

Memory recall is a skill for Claude Code, Codex from binary16labs/prime-silo. It costs 70 tokens per session (721 once invoked), scanned A, original, MIT.

A connection to Memo-Ray, a memory graph of earlier agent sessions and the files and actions they involved.

In plain words
What is it for?
Finding recent sessions, searching past work, identifying sessions that touched files, viewing the history of a change, and checking memory-system status.
Why use it?
It helps recover project history when nobody remembers which session handled a task or changed a particular file.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/binary16labs/prime-silo/memory-recall
Any agent
npx skills add binary16labs/prime-silo --skill memory-recall
Clone the repo
git clone --depth 1 https://github.com/binary16labs/prime-silo

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for Memory recall

README.md
[![agentmods](https://agentmods.dev/badge/skills/binary16labs/prime-silo/memory-recall.svg)](https://agentmods.dev/skills/binary16labs/prime-silo/memory-recall)
Your own site
<a href="https://agentmods.dev/skills/binary16labs/prime-silo/memory-recall"><img src="https://agentmods.dev/badge/skills/binary16labs/prime-silo/memory-recall.svg" alt="Measured on agentmods" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 721 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00070 $0.00721
Opus 5 $0.00035 $0.00360
Sonnet 5 $0.00014 $0.00144
Haiku 4.5 $0.00007 $0.00072

Measured 3d ago against content hash e531cd64d249, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Memory 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.

The scan reads SKILL.md. This mod also ships 1 executable file (memory-recall.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

app/L0/_all/mod/_prime_silo/memoray_client/ext/skills/memory-recall/SKILL.md · 60 lines

What it actually says

Use this skill when the user asks about their own history — past sessions, what they were working on, which sessions touched a file, or the lineage of a piece of work. The answers come from the Memo-Ray memory graph, the third graph of the cognitive mesh (beside the knowledge graph and the code graph). You query it; the user should never have to be their own institutional memory.

load helper

  • await import("/mod/_prime_silo/memoray_client/ext/skills/memory-recall/memory-recall.js")
  • All calls go through the shell proxy (/api/memoray); no endpoint configuration needed.
  • If a call throws "Memo-Ray is offline" or "disabled", relay that to the user with the fix (boot scripts/memoray.ps1, or enable it in the configuration wizard) — do not retry in a loop.

helpers

  • recentSessions({ agent?, limit? }) -> [{ id, title, agent, project, timestamp, link }]
  • search(query) -> { sessions:[{…, link}], files, actions } (omnibar across sessions/files/actions)
  • overview() -> { claude, antigravity, totalNodes, lastSync } ecosystem totals
  • sessionGraph(sessionId) -> { nodes, links } full lineage of one session
  • filesTouched(query) -> [{ fileName, filePath, agent }]
  • sessionLink(sessionId) -> deep link string into the visual memory page

guidance

  • ALWAYS cite the session id and include the deep link (link, or sessionLink(id)#/_prime_silo/memory?session_id=<id>) so the user can open the visual lineage at the memory page. Format as a markdown link to the hash route.
  • Prefer search(...) for "which sessions touched X" or fuzzy questions; prefer recentSessions(...) for "what was I working on".
  • Summarize — don't dump raw JSON. Lead with the answer (e.g. "You last worked on the lineage widget 2 hours ago"), then offer the link.
  • This is read-only. You cannot modify the memory graph; you observe it.

examples Recent work

const memory =
  await import("/mod/_prime_silo/memoray_client/ext/skills/memory-recall/memory-recall.js");
const sessions = await memory.recentSessions({ limit: 5 });
return sessions;

Which sessions touched a file

const memory =
  await import("/mod/_prime_silo/memoray_client/ext/skills/memory-recall/memory-recall.js");
return await memory.search("memoray_proxy.js");

Lineage of a specific session

const memory =
  await import("/mod/_prime_silo/memoray_client/ext/skills/memory-recall/memory-recall.js");
const graph = await memory.sessionGraph("<session-id>");
return {
  nodes: graph.nodes.length,
  links: graph.links.length,
  link: memory.sessionLink("<session-id>")
};
Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 3d ago First seen · 60 lines · 70 tokens per session scan A e531cd64d249

Subscribe to this mod's changes

Memory recall is a skill published in the GitHub repository binary16labs/prime-silo (5 stars, last pushed 10d ago), licensed MIT. It adds 70 tokens to every session and 721 once invoked, about $0.0003 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.