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-retrogit 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-retro)<a href="https://agentmods.dev/skills/iamtouchskyer/memex/memex-retro"><img src="https://agentmods.dev/badge/skills/iamtouchskyer/memex/memex-retro.svg" alt="Measured on agentmods" 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.00017 | $0.01624 |
| Opus 5 | $0.00009 | $0.00812 |
| Sonnet 5 | $0.00003 | $0.00325 |
| Haiku 4.5 | $0.00002 | $0.00162 |
Grade A, and why
memex-retro 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Retro
You have access to a Zettelkasten memory system via the memex CLI. After completing this task, reflect on what you learned and save valuable insights.
Tools Available
Three equivalent interfaces — use whichever your environment supports:
| CLI (memex in PATH) | Plugin CLI fallback (Claude Code) | MCP tool (VSCode / Cursor) |
|---|---|---|
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 write <slug> |
node ~/.claude/plugins/cache/cc-plugins/memex/*/dist/cli.js write <slug> |
memex_write with slug arg and body |
Resolution order: Try memex in PATH first. If not found, define a shell function and use it:
# Define once per session — DO NOT use variable assignment ($VAR won't expand correctly in zsh)
memex() { node $HOME/.claude/plugins/cache/cc-plugins/memex/*/dist/cli.js "$@"; }
# Then use normally
memex search "some query"
memex read some-slug
memex write some-slug << 'EOF'
card content here
EOF
If both CLI approaches fail, use MCP tools (memex_search, memex_read, memex_write).
The rest of this skill uses memex CLI syntax for brevity.
Process
digraph retro {
"Task completed" -> "Distill: what insights came from this task?";
"Distill: what insights came from this task?" -> "Any insights worth keeping?" [shape=diamond];
"Any insights worth keeping?" -> "Done, no card written" [label="no"];
"Any insights worth keeping?" -> "For each insight: draft atomic card" [label="yes"];
"For each insight: draft atomic card" -> "Fact Hygiene Check (WHO/WHAT-WHEN/RELATIONSHIP)";
"Fact Hygiene Check (WHO/WHAT-WHEN/RELATIONSHIP)" -> "Ambiguity found?" [shape=diamond];
"Ambiguity found?" -> "Fix draft: make implicit context explicit" [label="yes"];
"Fix draft: make implicit context explicit" -> "Fact Hygiene Check (WHO/WHAT-WHEN/RELATIONSHIP)";
"Ambiguity found?" -> "memex search for related existing cards" [label="no"];
"memex search for related existing cards" -> "memex read candidates";
"memex read candidates" -> "Existing card covers same insight?" [shape=diamond];
"Existing card covers same insight?" -> "Update existing card (append new info)" [label="yes"];
"Existing card covers same insight?" -> "Write new card with [[links]]" [label="no"];
"Update existing card (append new info)" -> "memex write <existing-card>";
"Write new card with [[links]]" -> "memex write <new-card>";
"memex write <existing-card>" -> "More insights?" [shape=diamond];
"memex write <new-card>" -> "More insights?" [shape=diamond];
"More insights?" -> "For each insight: draft atomic card" [label="yes"];
"More insights?" -> "Done" [label="no"];
}
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 · 115 lines · 17 tokens per session scan A 6ed5d330660b
memex-retro is a skill published in the GitHub repository iamtouchskyer/memex (141 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 1,624 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.