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/mandelbro/awesome-claude-hooksWrote 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/mandelbro/awesome-claude-hooks/memory-manager)<a href="https://agentmods.dev/commands/mandelbro/awesome-claude-hooks/memory-manager"><img src="https://agentmods.dev/badge/commands/mandelbro/awesome-claude-hooks/memory-manager/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/mandelbro/awesome-claude-hooks/memory-manager"><img src="https://agentmods.dev/badge/commands/mandelbro/awesome-claude-hooks/memory-manager.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.00000 | $0.00280 |
| Opus 5 | $0.00000 | $0.00140 |
| Sonnet 5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
memory-manager 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 8d 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 memory-manager — 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.
What it actually says
SPARC Memory Manager Mode
Purpose
Knowledge management with Memory tools for persistent insights.
Activation
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "memory-manager",
task_description: "organize project knowledge",
options: {
namespace: "project",
auto_organize: true
}
}
Option 2: Using NPX CLI (Fallback when MCP not available)
# Use when running from terminal or MCP tools unavailable
npx claude-flow sparc run memory-manager "organize project knowledge"
# For alpha features
npx claude-flow@alpha sparc run memory-manager "organize project knowledge"
Option 3: Local Installation
# If claude-flow is installed locally
./claude-flow sparc run memory-manager "organize project knowledge"
Core Capabilities
- Knowledge organization
- Information retrieval
- Context management
- Insight preservation
- Cross-session persistence
Memory Strategies
- Hierarchical organization
- Tag-based categorization
- Temporal tracking
- Relationship mapping
- Priority management
Knowledge Operations
- Store critical insights
- Retrieve relevant context
- Update knowledge base
- Merge related information
- Archive obsolete data
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.
- 8d ago First seen · 55 lines · 0 tokens per session scan A 94608382b51c
memory-manager is a command published in the GitHub repository mandelbro/awesome-claude-hooks (1 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 280 tokens. A static security scan graded it A with 0 findings. It is 100% identical to memory-manager, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
setup-context
Set up your Skill Memory — a pm-context.md every skill reads so outputs come back tailored to you.
brain
Set up or use your Professional Brain — init, ingest, recall, or review.
pull-learnings
Pulls shared organization patterns into local org-patterns.toon.
context-stats
Display context window usage and token statistics.
meetings-list
List recent meetings and voice memos. Use when the user asks "what meetings did I have", "show my recent recordings", "any meetings today", "list my voice memos", or wants an overview of their meeting history. Also use when they need to find a specific meeting by browsing rather than searching.
meetings-search
Search meeting transcripts and voice memos for people, topics, decisions, commitments, or remembered ideas. Use when the user asks what was discussed, decided, or said across their meeting history. Not for preparing an upcoming meeting; use $meetings-prep.