Borrowing it
Nothing to install: this file belongs to EarthmanWeb/claude-flow-plugin. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/EarthmanWeb/claude-flow-plugin/main/.claude/commands/claude-flow-memory.mdgit clone --depth 1 https://github.com/EarthmanWeb/claude-flow-pluginWrote 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/earthmanweb/claude-flow-plugin/claude-flow-memory)<a href="https://agentmods.dev/commands/earthmanweb/claude-flow-plugin/claude-flow-memory"><img src="https://agentmods.dev/badge/commands/earthmanweb/claude-flow-plugin/claude-flow-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.
<a href="https://agentmods.dev/commands/earthmanweb/claude-flow-plugin/claude-flow-memory"><img src="https://agentmods.dev/badge/commands/earthmanweb/claude-flow-plugin/claude-flow-memory.svg" alt="Reviewed on agentmods" width="80" 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.00012 | $0.00651 |
| Opus 5.5 | $0.00005 | $0.00260 |
| Sonnet 5.5 | $0.00002 | $0.00130 |
| Haiku 4.5 | $0.00001 | $0.00065 |
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 1mo 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.
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.
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
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.
- 1mo ago First seen · 108 lines · 12 tokens per session scan A 0cbeed7c94dc
claude-flow-memory is a command published in the GitHub repository EarthmanWeb/claude-flow-plugin (2 stars, last pushed 8mo ago), licensed MIT. It adds 12 tokens to every session and 651 once invoked, about $0.0000 per session on Opus 5.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.
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.
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.
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.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.