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/init-memory-bankgit 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/init-memory-bank)<a href="https://agentmods.dev/commands/hudrazine/claude-code-memory-bank/init-memory-bank"><img src="https://agentmods.dev/badge/commands/hudrazine/claude-code-memory-bank/init-memory-bank.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.1 | $0.00013 | $0.01598 |
| Opus 5 | $0.00006 | $0.00799 |
| Sonnet 5 | $0.00003 | $0.00320 |
| Haiku 4.5 | $0.00001 | $0.00160 |
Grade A, and why
init-memory-bank 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 6d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Memory Bank System with Metacognitive Flow
Your Task
Think deeply about the project context and initialize the Memory Bank system using a metacognitive approach that ensures profound understanding and thoughtful implementation.
Initial Setup: Task Tracking
Use the TodoWrite tool to create a structured task list for this complex initialization process:
todos:
- Stage 1: Understanding and Context Recognition (pending)
- Stage 2: Preliminary Judgment Formation (pending)
- Stage 3: Critical Evaluation and Deep Analysis (pending)
- Stage 4: Adaptive Strategy with Confidence Scoring (pending)
- Stage 5: Reflective Implementation (pending)
- Stage 6: Final Metacognitive Assessment (pending)
Update each task status as you progress:
- Mark as
in_progresswhen starting a stage - Mark as
completedonly when fully satisfied with that stage - Add sub-tasks if a stage reveals complex requirements
Stage 1: Understanding and Context Recognition
Metacognitive Understanding Phase Before any action, deeply understand:
- What is the true purpose of this initialization?
- What assumptions am I making about this project?
- What context clues should I be aware of?
Use the Task tool with this enhanced prompt:
"Perform a metacognitive analysis of the current project:
- Initial observations about project state
- What this tells me about the project's nature
- What I might be assuming incorrectly
- Alternative interpretations of the project structure
- Confidence level in my initial assessment (0-100%)
Then provide standard analysis:
- Current working directory path
- Memory Bank directory status
- Project type detection (package.json, requirements.txt, etc.)
- Technologies and frameworks
- Project structure overview
- Existing documentation"
Self-Reflection Questions:
- Am I seeing the full picture?
- What might I be missing?
- How does my interpretation align with reality?
Stage 2: Preliminary Judgment Formation
Based on initial understanding, form hypotheses:
- What type of Memory Bank would best serve this project?
- What initialization approach seems most appropriate?
- What are my intuitions telling me?
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.
- 6d ago First seen · 213 lines · 13 tokens per session scan A f375ba582c50
init-memory-bank is a command published in the GitHub repository hudrazine/claude-code-memory-bank (41 stars, last pushed 1y ago), licensed Unlicense. It adds 13 tokens to every session and 1,598 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
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.
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.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
music-suno-prompt
Grounded Suno prompt synthesis from local knowledge corpus + persona canon + label canon. No vibes-prompting.