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/commit)<a href="https://agentmods.dev/commands/lucasrosati/claude-code-memory-setup/commit"><img src="https://agentmods.dev/badge/commands/lucasrosati/claude-code-memory-setup/commit/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/commit"><img src="https://agentmods.dev/badge/commands/lucasrosati/claude-code-memory-setup/commit.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.00277 |
| Opus 5.5 | $0.00000 | $0.00111 |
| Sonnet 5.5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
commit 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 today.
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
/commit — Commit + Push + Auto-save
When you receive this command, do the following:
1. Analyze changes
- Run
git statusandgit diff --statto see what changed - Read the modified files to understand the context
2. Generate the commit message
- Write a concise, descriptive commit message
- Format: "type: short description" (e.g. "feat: leitner flashcards", "fix: auth redirect loop", "refactor: componentized sidebar")
- If there are several changes, use the most significant one as the main message
3. Execute
git add .git commit -m "generated message"git push
4. Auto-save (session log + memory)
After the commit and the push, read ~/.claude/commands/save.md and run Phases 1 and 2 in full, adding this section to the session log:
## Commit
- Short hash, message, files changed
Rules
- Never commit without showing
git statusfirst - Always show the generated commit message before executing
- If there are files that shouldn't be committed (env, node_modules, etc.), warn the user
- Wait for the user's confirmation before running the commit
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.
- today First seen · 31 lines · 0 tokens per session scan A c6e08dc81723
commit is a command published in the GitHub repository lucasrosati/claude-code-memory-setup (1,037 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 277 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
speckit.companion.living-sync
Sync living specs from your current changes — group working-tree changes (uncommitted included) by capability and update every affected spec in one pass (opt-in, update-not-regenerate, never halts).
pre-commit-check
Tu es un assistant de qualité code. Tu dois effectuer toutes les vérifications nécessaires AVANT de créer un commit, pour garantir que le code respecte les standards du projet.
fest-commit
Commit changes with festival traceability metadata.
pre-commit-audit
Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers. Use when the user requests a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode…
merge
You are executing the /hydra:merge command. Merge a worktree branch back into the current branch.
sync-tutorials
Commit and push your tutorials to the GitHub repository for backup and mobile reading.