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.
git clone --depth 1 https://github.com/f-amine/vibe-stackWrote 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/f-amine/vibe-stack/claude-flow-memory)<a href="https://agentmods.dev/commands/f-amine/vibe-stack/claude-flow-memory"><img src="https://agentmods.dev/badge/commands/f-amine/vibe-stack/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/f-amine/vibe-stack/claude-flow-memory"><img src="https://agentmods.dev/badge/commands/f-amine/vibe-stack/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 f-amine/vibe-stack (21 stars, last pushed 3mo 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
new
Scaffold a new Better-T-Stack project. Plans a full, validated stack with the Better-T-Stack MCP server, confirms it, then generates the project.
add
Add addons/features (PWA, Tauri, docs, linters, task runners, MCP, …) to an existing Better-T-Stack project via the Better-T-Stack MCP server.
speckit.archive.run
Archive merged feature specs into project memory with provenance, sweep discovery, and gated cleanup.
archive
Archive merged feature specs into project memory with provenance, sweep discovery, and gated cleanup.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.