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/iamtouchskyer/memex/memex-agentic-memorynpx skills add iamtouchskyer/memex --skill memex-agentic-memorygit 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-agentic-memory)<a href="https://agentmods.dev/skills/iamtouchskyer/memex/memex-agentic-memory"><img src="https://agentmods.dev/badge/skills/iamtouchskyer/memex/memex-agentic-memory.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.00019 | $0.01606 |
| Opus 5 | $0.00010 | $0.00803 |
| Sonnet 5 | $0.00004 | $0.00321 |
| Haiku 4.5 | $0.00002 | $0.00161 |
Grade A, and why
memex-agentic-memory 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 5d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic Memory Skill (Experimental)
An A-MEM-inspired workflow that uses existing memex primitives to produce higher-quality memory cards through structured observation, enrichment, retrieval, and deliberate linking.
This skill is experimental and requires opt-in.
Prerequisite: Feature Flag Guard
Before proceeding, locate .memexrc using the same precedence as core memex:
$MEMEX_HOME/.memexrc(ifMEMEX_HOMEenv var is set)- Walk up from the current directory looking for
.memexrc ~/.memex/.memexrc(fallback)
Check that experimental.agenticMemory is exactly true.
If the flag is missing, false, or not exactly true, STOP. Use the standard
memex-retro skill instead. Do not proceed with the agentic workflow.
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, use the plugin
fallback or MCP tools.
Workflow
Step 1: Input Triage
Identify whether there is a memory-worthy insight from the completed work.
Skip if the content is:
- Temporary or session-specific (current task state, in-progress work)
- Obvious or well-known (standard library usage, common patterns)
- Not reusable across future sessions
If nothing is worth remembering, stop here.
Step 2: Draft Atomic Card
For each insight, draft one card:
- Title: Short, descriptive
- Slug: English kebab-case (e.g.,
yaml-array-roundtrip-bug) - Body: One atomic insight in your own words. Distill, don't copy.
- Context: Add explicit project/domain context when the insight would be ambiguous without it
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.
- 5d ago First seen · 201 lines · 19 tokens per session scan A 697adeac3cae
memex-agentic-memory is a skill published in the GitHub repository iamtouchskyer/memex (141 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 1,606 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…
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.
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.