What is claude-flow-memory?

A command-line memory store for saving and finding information across sessions and collaborating agents. It supports named namespaces, which are separate areas for organizing related information, plus backup and cleanup operations.

Use it to store architecture decisions and implementation details, search saved knowledge, view memory statistics, export or import backups, and remove old entries.

Important decisions and working context can otherwise be lost when a session ends or when different agents work separately. Persistent memory keeps that information available later.

claude-flow-memory — Command by f-amine

Install

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.

agentmods

npx agentmods add commands/f-amine/vibe-stack/claude-flow-memory

Clone the repo

git clone --depth 1 https://github.com/f-amine/vibe-stack

Made for: Claude Code.

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

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

Security scan A 0 findings. Scan, not verified.

Origin 100% copy Near-identical to another mod 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	$0.00012	$0.00651
Opus 5	$0.00006	$0.00326
Sonnet 5	$0.00002	$0.00130
Haiku 4.5	$0.00001	$0.00065

Measured 2d ago against content hash 0cbeed7c94dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

claude-flow-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 2d 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.

Origin

This is a copy

100% identical to claude-flow-memory — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/claude-flow-memory.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

🧠 Claude-Flow Memory System

The memory system provides persistent storage for cross-session and cross-agent collaboration with CRDT-based conflict resolution.

Store Information

# Store with default namespace
./claude-flow memory store "key" "value"

# Store with specific namespace
./claude-flow memory store "architecture_decisions" "microservices with API gateway" --namespace arch

Query Memory

# Search across all namespaces
./claude-flow memory query "authentication"

# Search with filters
./claude-flow memory query "API design" --namespace arch --limit 10

Memory Statistics

# Show overall statistics
./claude-flow memory stats

# Show namespace-specific stats
./claude-flow memory stats --namespace project

Export/Import

# Export all memory
./claude-flow memory export full-backup.json

# Export specific namespace
./claude-flow memory export project-backup.json --namespace project

# Import memory
./claude-flow memory import backup.json

Cleanup Operations

# Clean entries older than 30 days
./claude-flow memory cleanup --days 30

# Clean specific namespace
./claude-flow memory cleanup --namespace temp --days 7

🗂️ Namespaces

default - General storage
agents - Agent-specific data and state
tasks - Task information and results
sessions - Session history and context
swarm - Swarm coordination and objectives
project - Project-specific context
spec - Requirements and specifications
arch - Architecture decisions
impl - Implementation notes
test - Test results and coverage
debug - Debug logs and fixes

🎯 Best Practices

Naming Conventions

Use descriptive, searchable keys
Include timestamp for time-sensitive data
Prefix with component name for clarity

Organization

Use namespaces to categorize data
Store related data together
Keep values concise but complete

Maintenance

Regular backups with export
Clean old data periodically
Monitor storage statistics
Compress large values

Read the full file on GitHub · 108 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.

2d ago First seen · 108 lines · 12 tokens per session scan A 0cbeed7c94dc

Subscribe to this mod's changes

claude-flow-memory is a command published in the GitHub repository f-amine/vibe-stack (21 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 651 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to claude-flow-memory, differing in 0 lines, and is treated as a copy.

Memory and context ai better-auth claude claude-code drizzle-orm nextjs

claude-flow-memory