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/initgit 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.00927 |
| Opus 5 | $0.00006 | $0.00464 |
| Sonnet 5 | $0.00002 | $0.00185 |
| Haiku 4.5 | $0.00001 | $0.00093 |
Grade A, and why
init 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize auto-managed CLAUDE.md memory files for this project.
Workflow
Step 1: Configure Trigger Mode
Ask the user how auto-memory should trigger updates using AskUserQuestion:
Question: "How should auto-memory trigger CLAUDE.md updates?"
Options:
- default (recommended): Track file edits in real-time. Updates trigger after Edit/Write operations and file modifications (rm, mv, etc.). Best for most workflows.
- gitmode: Only trigger on git commits. Updates happen when you commit changes. Best for developers who commit frequently and prefer "if you didn't commit, it didn't happen" workflow.
Save the selection to .claude/auto-memory/config.json:
{
"triggerMode": "default"
}
Step 1a: Configure Memory File(s)
Ask the user which memory file(s) auto-memory should maintain using AskUserQuestion:
Question: "Which memory file(s) should auto-memory maintain?"
Options:
- CLAUDE.md only (default): Standard Claude Code memory file. Best for projects using Claude Code exclusively.
- AGENTS.md only: Memory stored in AGENTS.md. Best for projects using OpenAI Codex, Gemini, or other agents that read AGENTS.md.
- Both - AGENTS.md for content, CLAUDE.md redirects to it: AGENTS.md holds full memory; CLAUDE.md contains a one-line redirect. Best when multiple AI coding agents collaborate on the same repo.
Update .claude/auto-memory/config.json with the selection:
- CLAUDE.md only: omit
memoryFiles(or set"memoryFiles": ["CLAUDE.md"]) - AGENTS.md only:
"memoryFiles": ["AGENTS.md"] - Both:
"memoryFiles": ["CLAUDE.md", "AGENTS.md"]
When "Both" is selected, also generate the redirect CLAUDE.md at the project root using the CLAUDE.redirect.md.template - a static file with the single line: Read AGENTS.md in this directory for project context.
Step 1b: Configure Auto-Commit (Optional)
Ask the user if they want CLAUDE.md changes auto-committed using AskUserQuestion:
Question: "Should auto-memory automatically commit CLAUDE.md changes after 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 · 98 lines · 12 tokens per session scan A 3fa9d0291843
init 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 927 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.