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/hudrazine/claude-code-memory-bank/update-memorygit clone --depth 1 https://github.com/hudrazine/claude-code-memory-bankWrote 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/hudrazine/claude-code-memory-bank/update-memory)<a href="https://agentmods.dev/commands/hudrazine/claude-code-memory-bank/update-memory"><img src="https://agentmods.dev/badge/commands/hudrazine/claude-code-memory-bank/update-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.00007 | $0.00881 |
| Opus 5 | $0.00003 | $0.00441 |
| Sonnet 5 | $0.00001 | $0.00176 |
| Haiku 4.5 | $0.00001 | $0.00088 |
Grade A, and why
update-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 4d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Bank Documentation Update
Task
Think longer about project evolution and comprehensively review all Memory Bank files to preserve important learnings, decisions, and project state for future Claude Code sessions. Ensure they accurately reflect the current project state and recent developments.
Process
1. Comprehensive Review
Review all Memory Bank files in order:
- projectbrief.md - Core project information
- productContext.md - Product decisions and user experience
- systemPatterns.md - Architecture and design patterns
- techContext.md - Technologies and tools
- activeContext.md - Current focus and next steps
- progress.md - Development milestones and status
2. Update Criteria
Document changes when:
- New patterns established: Coding patterns, architectural decisions, workflows
- Significant features completed: Major functionality, integrations, systems
- Important discoveries made: Technical insights, constraint clarifications, solutions
- Project direction changes: Scope adjustments, priority shifts, approach changes
- Challenges resolved: How problems were solved for future reference
3. Update Guidelines
For projectbrief.md:
- Core requirements changes
- Scope adjustments
- Major goal revisions
- Fundamental constraint updates
For productContext.md:
- User experience insights
- Problem definition refinements
- Solution approach changes
- Value proposition updates
For activeContext.md:
- Current development phase and focus
- Recently completed work
- Active challenges and blockers
- Next priority actions
- Important decisions in progress
For progress.md:
- Feature completion status
- Development milestone achievements
- Recent updates with dates
- Current challenges and risks
For systemPatterns.md:
- New design patterns adopted
- Architectural decisions made
- Integration approaches established
- Security or performance patterns
For techContext.md:
- New technologies added
- Configuration changes
- Development workflow updates
- Environment setup changes
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.
- 4d ago First seen · 131 lines · 7 tokens per session scan A adf00eed594f
update-memory is a command published in the GitHub repository hudrazine/claude-code-memory-bank (41 stars, last pushed 1y ago), licensed Unlicense. It adds 7 tokens to every session and 881 once invoked, about $0.0000 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
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
neo-review
Get Neo's code review with semantic matching against past findings in memory. Use on a diff or module before merge, especially where earlier mistakes in this codebase are likely to recur. Skip for formatting, lint-catchable issues, and single-line changes.