Claude Code Memory Setup is a workflow that gives Claude Code persistent project memory and selected codebase context using Obsidian notes, chat imports, and Graphify knowledge graphs. Developers use it to retain decisions between sessions and retrieve relevant code information without repeatedly reading the whole repository. Its catalogue commands support this memory and code-context workflow.
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.
git clone --depth 1 https://github.com/lucasrosati/claude-code-memory-setupWrote 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/commands/lucasrosati/claude-code-memory-setup/memorize)<a href="https://agentmods.dev/commands/lucasrosati/claude-code-memory-setup/memorize"><img src="https://agentmods.dev/badge/commands/lucasrosati/claude-code-memory-setup/memorize/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/commands/lucasrosati/claude-code-memory-setup/memorize"><img src="https://agentmods.dev/badge/commands/lucasrosati/claude-code-memory-setup/memorize.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00284 |
| Opus 5.5 | $0.00000 | $0.00114 |
| Sonnet 5.5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
memorize 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 yesterday.
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
/memorize — Update Permanent Memory
Pins a decision, insight or convention to the vault right away. /save already does this automatically at the end of the session; use this command only when you want to write something now, mid-session.
When you receive this command, do the following:
- Read
~/.claude/commands/save.md. Run the "Vault detection" block to get<vault>and<project>. - With an argument (the item to memorize): run steps 2.2 to 2.5 of Phase 2 for the given item. If the item meets none of the 2.1 criteria, say why and don't write.
- Without an argument: run the whole Phase 2, starting at 2.1, over the current session. Items that a /save in this session already wrote count as "already memorized with no change".
- Don't create a session log: step 2.4 only applies if a log for this session already exists (from an earlier /save); in that case, update its "Notes created or updated" section.
- In the 2.5 report, omit the "Session log" line if none was touched.
- If nothing was written, don't write any file and end the reply with this exact line:
Memory: nothing new to memorize.
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.
- yesterday First seen · 14 lines · 0 tokens per session scan A b55bc4f6c0a9
memorize is a command published in the GitHub repository lucasrosati/claude-code-memory-setup (1,038 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 284 tokens. 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-10-22.
Other commands, from other repositories
save-memory
You are saving what you learned this session into the megamemory knowledge graph. This is YOUR memory — record anything valuable for future sessions: what you understood about the project, what you built, decisions that were made, patterns you noticed, or intent the user shared.
bootstrap-memory
RUN { git ls-files; git ls-files --others --exclude-standard; } 2>/dev/null | sort -u | xargs wc -l 2>/dev/null | sort -rn | head -150 READ README.md.
handoff
Create, accept, or update the persistent .context/ai-handoff.md state shared by AI sessions and machines. Use when continuing in a new Claude or Codex session, transferring work between clients, or recording ownership and restart state.
speckit.archive
Archive a feature specification into main project memory after merge, resolving gaps and conflicts.
memory-search
Search agent memory + learned patterns for cross-session context relevant to $ARGUMENTS.
slm-bot-memory
Cross-bot memory on a shared computer (Grok Bot, Cursor plugin, any host where several agents share one machine). Explains agentid attribution vs. profile/scope access, how to namespace by agentid + profile + scope, and what must never be written to memory. Read this before the first remember/recall on a new…