What is update-memory?

A command that reviews and updates Memory Bank files with important project changes, discoveries, decisions, and progress.

Use it after significant changes or completed work to record the project's current state.

It keeps project context accurate so later coding sessions do not lose important information.

How hudrazine/claude-code-memory-bank configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to hudrazine/claude-code-memory-bank. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/hudrazine/claude-code-memory-bank/main/.claude/commands/workflow/update-memory.md

Clone the repo

git clone --depth 1 https://github.com/hudrazine/claude-code-memory-bank

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/hudrazine/claude-code-memory-bank/update-memory/github.svg)](https://agentmods.dev/commands/hudrazine/claude-code-memory-bank/update-memory)

Your own site

<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/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.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 881 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00007	$0.00881
Opus 5.5	$0.00003	$0.00352
Sonnet 5.5	$0.00001	$0.00176
Haiku 4.5	$0.00001	$0.00088

Measured 2mo ago against content hash adf00eed594f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/commands/workflow/update-memory.md · 131 lines

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

Read the full file on GitHub · 131 lines

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.

2mo ago First seen · 131 lines · 7 tokens per session scan A adf00eed594f

Subscribe to this mod's changes

update-memory is a command published in the GitHub repository hudrazine/claude-code-memory-bank (42 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.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.

Memory and context

update-memory next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
update-memoryhudrazine/claude-code-memory-bank	Command	42	1y ago	Unlicense	A	7	Claude Code
minutes-ideassilverstein/minutes	Command	1.6k	yesterday	MIT	A	48	Claude Code, OpenCode
learnReflexioAI/claude-smart	Command	791	3d ago	Apache-2.0	A	14	Claude Code
memory-storeverygoodplugins/mcp-automem	Command	66	today	MIT	A	10	Claude Code
analyze-contextRohiRIK/OpenLtm	Command	29	8d ago	MIT	A	39	Claude Code
cc-memoryTheLobbi/claude	Command	21	7d ago	MIT	A	0	Claude Code
lians-recallLians-ai/Lians	Command	17	5d ago	Apache-2.0	A	19	Claude Code

claude-code-memory-bank: Command for Claude Code