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 skills/sam-ueckert/oc-memory/recallnpx skills add sam-ueckert/oc-memory --skill recallgit clone --depth 1 https://github.com/sam-ueckert/oc-memoryWrote 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/skills/sam-ueckert/oc-memory/recall)<a href="https://agentmods.dev/skills/sam-ueckert/oc-memory/recall"><img src="https://agentmods.dev/badge/skills/sam-ueckert/oc-memory/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.00074 | $0.00450 |
| Opus 5 | $0.00037 | $0.00225 |
| Sonnet 5 | $0.00015 | $0.00090 |
| Haiku 4.5 | $0.00007 | $0.00045 |
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 4d 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
Recall
Multi-layer memory retrieval: structured DB first, markdown fallback, grep sweep.
Workflow
-
Structured search — fast, ranked, typed cells:
mem search "<query>"Returns cell ID, type, scene, salience, and content snippet.
-
Markdown memory search — if the platform provides
memory_search, use it:memory_search(query="<query>")Then
memory_get(path, from, lines)to pull relevant snippets. -
Grep fallback — catch anything the other layers missed:
grep -ri "<keyword>" memory/ MEMORY.md -
Synthesize — combine results across layers. Cite sources when helpful:
- Structured:
[cell #ID, scene:<scene>] - Markdown:
Source: <path>#<line>
- Structured:
Guidelines
- Run all applicable layers (don't stop at the first hit — cross-reference).
- For ambiguous single-word queries, search broadly then ask for clarification if results are thin.
- If nothing is found across all layers, say so clearly.
- When results exist but are sparse, mention what you found and offer to dig deeper.
- Never fabricate memories. Only report what's actually stored.
Storing New Memories
If the recall process surfaces a gap worth filling, offer to store it:
mem quick-store <scene> <type> <salience> "<content>"
Cell types: fact, decision, preference, task, risk, plan, lesson
Salience: 0.1 (trivia) → 0.5 (normal) → 0.8 (important) → 1.0 (critical)
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.
- 4d ago First seen · 50 lines · 74 tokens per session scan A 6ae895745de9
recall is a skill published in the GitHub repository sam-ueckert/oc-memory (2 stars, last pushed 22d ago), licensed MIT. It adds 74 tokens to every session and 450 once invoked, about $0.0004 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 skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…