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 commands/severity1/claude-code-auto-memory/syncgit clone --depth 1 https://github.com/severity1/claude-code-auto-memoryWhat 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.00012 | $0.00419 |
| Opus 5 | $0.00006 | $0.00210 |
| Sonnet 5 | $0.00002 | $0.00084 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
sync 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
Detect files changed outside Claude Code and update CLAUDE.md incrementally.
Use this when you've edited files manually (outside Claude Code) and want to update CLAUDE.md without a full recalibration.
Workflow
-
Check if git repo: Run
git rev-parse --is-inside-work-tree- If not a git repo: Report error and suggest
/auto-memory:calibrateinstead
- If not a git repo: Report error and suggest
-
Detect changed files using git:
git diff --name-only HEAD # Modified tracked files git diff --cached --name-only # Staged files git ls-files --others --exclude-standard # New untracked files -
Filter files (exclude from processing):
- Files in
.claude/directory - Memory files: read
memoryFilesfrom.claude/auto-memory/config.json(default["CLAUDE.md"]) and exclude any file whose name appears in that list - Files outside project directory
- Files in
-
If no changes detected: Report "Already in sync - no manual changes found"
-
If changes found:
- Convert paths to absolute paths
- Write to
.claude/auto-memory/dirty-files(one path per line, ordirty-files-{session_id}if session_id is available from the environment) - Use the Task tool to spawn the
memory-updateragent with prompt: "Update [active memory file] for manually changed files: [file list]" (use AGENTS.md or CLAUDE.md per the memoryFiles config)
-
Report summary: List files that were processed
Notes
- Requires a git repository for change detection
- For non-git projects or full recalibration, use
/auto-memory:calibrateinstead - The memory-updater agent handles the actual CLAUDE.md updates
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 · 41 lines · 12 tokens per session scan A 672d2837eb3f
sync is a command published in the GitHub repository severity1/claude-code-auto-memory (157 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 419 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.