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 skills add iamtouchskyer/memex --skill memex-recallgit clone --depth 1 https://github.com/iamtouchskyer/memexWrote 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/iamtouchskyer/memex/memex-recall)<a href="https://agentmods.dev/skills/iamtouchskyer/memex/memex-recall"><img src="https://agentmods.dev/badge/skills/iamtouchskyer/memex/memex-recall/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/skills/iamtouchskyer/memex/memex-recall"><img src="https://agentmods.dev/badge/skills/iamtouchskyer/memex/memex-recall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00023 | $0.01277 |
| Opus 5 | $0.00012 | $0.00639 |
| Sonnet 5 | $0.00005 | $0.00255 |
| Haiku 4.5 | $0.00002 | $0.00128 |
Grade A, and why
memex-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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Recall
You have access to a Zettelkasten memory system via the memex CLI. Before starting this task, search your memory for relevant prior knowledge.
Tools Available
Three equivalent interfaces — use whichever your environment supports:
| CLI (memex in PATH) | Plugin CLI fallback (Claude Code) | MCP tool (VSCode / Cursor) |
|---|---|---|
memex read index |
node ~/.claude/plugins/cache/cc-plugins/memex/*/dist/cli.js read index |
memex_read with slug index |
memex search <q> |
node ~/.claude/plugins/cache/cc-plugins/memex/*/dist/cli.js search <q> |
memex_search with query arg |
memex read <slug> |
node ~/.claude/plugins/cache/cc-plugins/memex/*/dist/cli.js read <slug> |
memex_read with slug arg |
memex search (no args) |
node ~/.claude/plugins/cache/cc-plugins/memex/*/dist/cli.js search |
memex_search with no args |
Resolution order: Try memex in PATH first. If not found, define a shell function and use it:
memex() { node $HOME/.claude/plugins/cache/cc-plugins/memex/*/dist/cli.js "$@"; }
If both CLI approaches fail, use MCP tools.
The rest of this skill uses memex CLI syntax for brevity.
Process
digraph recall {
"Task received" -> "Relevant to prior work?" [shape=diamond];
"Relevant to prior work?" -> "Generate 1-3 search keywords" [label="yes"];
"Relevant to prior work?" -> "Proceed without recall" [label="no"];
"Generate 1-3 search keywords" -> "memex search <query>";
"memex search <query>" -> "Review summaries";
"Review summaries" -> "Relevant cards found?" [shape=diamond];
"Relevant cards found?" -> "memex read <card>" [label="yes"];
"Relevant cards found?" -> "Need broad overview?" [label="no"];
"Need broad overview?" -> "memex read index" [label="yes"];
"Need broad overview?" -> "Proceed without recall" [label="no"];
"memex read index" -> "Pick relevant slugs" -> "memex read <card>";
"memex read <card>" -> "See [[links]] in content";
"See [[links]] in content" -> "Links worth following?" [shape=diamond];
"Links worth following?" -> "memex read <linked-card>" [label="yes"];
"Links worth following?" -> "Enough context?" [label="no"];
"memex read <linked-card>" -> "See [[links]] in content";
"Enough context?" -> "More queries to try?" [label="no"];
"More queries to try?" -> "Generate new query" [label="yes"];
"Generate new query" -> "memex search <query>";
"More queries to try?" -> "Summarize findings, proceed with task" [label="no"];
"Enough context?" -> "Summarize findings, proceed with task" [label="yes"];
}
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.
- 9d ago First seen · 95 lines · 23 tokens per session scan A c8e9ebe3e5df
memex-recall is a skill published in the GitHub repository iamtouchskyer/memex (141 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 1,277 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-30.
Other skills, from other repositories
memory-curation
When you have read / processed a workspace asset in this session and learned something durable about it, write a memory page so future sessions benefit. Maintain the workspace wiki's hierarchical structure as it grows.
memory
Persist and retrieve agent memory across sessions — write durable notes, read by path, recall via semantic search, list/delete, and consolidate. Use whenever the user asks to remember/forget something, when you need to look up past decisions or context, or when episodic state matters beyond the current turn. Executes…
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
recall
Recall this repository's OwnMem local memory before changing code, and keep it healthy. Use when a repository contains .ownmem/, when past debugging lessons could apply ("have we hit this before", "why is it done this way"), or when the user mentions ownmem, project memory, or recalling across sessions.