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/sethdford/flowx/flowx-memorygit clone --depth 1 https://github.com/sethdford/flowxWrote 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/sethdford/flowx/flowx-memory)<a href="https://agentmods.dev/commands/sethdford/flowx/flowx-memory"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/flowx-memory.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 | $0.00014 | $0.01108 |
| Opus 5 | $0.00007 | $0.00554 |
| Sonnet 5 | $0.00003 | $0.00222 |
| Haiku 4.5 | $0.00001 | $0.00111 |
Grade A, and why
flowx-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 4d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FlowX Memory System (Batchtools Optimized)
The memory system provides persistent storage with enhanced batch operations for efficient cross-session and cross-agent collaboration.
Batch Store Operations
# Single store (traditional)
npx flowx memory store "key" "value" --namespace project
# Batch store multiple key-value pairs
npx flowx memory batch-store --data '{
"project_specs": "e-commerce platform requirements",
"api_design": "RESTful API architecture",
"db_schema": "PostgreSQL database design"
}' --namespace project
# Bulk import from file
npx flowx memory bulk-import data.json --parallel
Parallel Query Operations
# Single query (traditional)
npx flowx memory query "search term" --limit 10
# Parallel multi-term search
npx flowx memory batch-query --terms "api,database,authentication" --parallel
# Cross-namespace parallel search
npx flowx memory multi-query "pattern" --namespaces "all" --concurrent
Batch Statistics & Analysis
# Comprehensive stats across all namespaces
npx flowx memory batch-stats --detailed --parallel
# Analyze memory usage patterns
npx flowx memory analyze --patterns --concurrent
# Generate usage reports
npx flowx memory batch-report --format "json,csv,html"
Bulk Export/Import Operations
# Export multiple namespaces concurrently
npx flowx memory batch-export --namespaces "project,agents,tasks" --output exports/
# Parallel import with validation
npx flowx memory batch-import --files "*.json" --validate --parallel
# Incremental backup with compression
npx flowx memory backup --incremental --compress --parallel
Enhanced Namespace Operations
# Create multiple namespaces
npx flowx memory batch-create-ns "feature1,feature2,feature3"
# Clone namespaces in parallel
npx flowx memory batch-clone --source project --targets "dev,test,prod"
# Merge namespaces concurrently
npx flowx memory batch-merge --sources "temp1,temp2" --target main
Advanced Batch Operations
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.
- 4d ago First seen · 171 lines · 14 tokens per session scan A 0268c9b4e45e
flowx-memory is a command published in the GitHub repository sethdford/flowx (2 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 1,108 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-31.
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.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
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.