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.5 | $0.00009 | $0.00511 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 95 lines · 23 tokens per session scan A c8e9ebe3e5df
memex-recall is a skill published in the GitHub repository iamtouchskyer/memex (144 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 1,277 once invoked, about $0.0001 per session on Opus 5.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
Persist and retrieve agent memory across sessions — recall via the three-stage protocol (structure route → semantic search → navigation fallback), read via memoryload, see the wiki structure via memorybrowse, write well-placed pages via memorywrite (including section-level append/rewrite), maintain via memorycurate.…
memory-dream
Curate the workspace memory wiki as its appointed orchestrator. Trigger on a Cloud-scheduled Dream task or a user's direct curation request. Inspect candidates for orphan leaves, near-duplicates, stale pages, remote conflicts and oversized hubs; browse the graph, cluster leaves into INDEX/hub/leaf structure, maintain…
memory-import
Bulk-import an external knowledge base into Prismer memory via the three-layer import pipeline (07 §3.1). Use when the user asks to import/migrate documents, a knowledge base, or notes into workspace memory. Layer 1 lands raw documents (zero LLM, instantly searchable); Layer 2 is YOUR distillation work — you read the…
prismer-obsidian
Read, search, create, and edit notes in the Obsidian vault.
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.