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/michael-denyer/memory-mcp/test-allgit clone --depth 1 https://github.com/michael-denyer/memory-mcpWrote 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/michael-denyer/memory-mcp/test-all)<a href="https://agentmods.dev/commands/michael-denyer/memory-mcp/test-all"><img src="https://agentmods.dev/badge/commands/michael-denyer/memory-mcp/test-all.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.00009 | $0.00732 |
| Opus 5 | $0.00005 | $0.00366 |
| Sonnet 5 | $0.00002 | $0.00146 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
test-all 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 3d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory MCP Live Testing
Run /memory-mcp:test-all to start a guided testing session. Walk through each phase, execute tests, and track results.
Execution Modes
Ask user which approach:
- Full suite - Run all 12 phases sequentially with pauses between
- Specific phase - Run just one phase (1-12)
- Smoke test - Quick 2-minute sanity check
Quick Smoke Test
For a 2-minute sanity check:
mcp__memory__remember("Smoke test", tags=["smoke"]) # → get ID
mcp__memory__recall("smoke")
mcp__memory__promote(id)
mcp__memory__hot_cache_status()
mcp__memory__demote(id)
mcp__memory__forget(id)
mcp__memory__memory_stats()
Test Phases
| Phase | Name | Tests |
|---|---|---|
| 1 | Core Operations | remember, recall, forget |
| 2 | Hot Cache | promote, demote, pin, unpin |
| 3 | Knowledge Graph | link, unlink, traverse |
| 4-5 | Trust & Contradictions | validate, invalidate, resolve |
| 6 | Sessions | episodic memory, summarize |
| 7 | Mining | log_output, run_mining, approve |
| 8 | Seeding | seed_from_text, bootstrap |
| 9-10 | Predictive & Quality | predict_next, mark_used |
| 11 | Maintenance | db_info, cleanup, consolidate |
| 12 | Resources | hot-cache, working-set |
| 14 | Edge Cases | error handling |
| 15 | Cleanup | remove test data |
Test Tracking
Track results as you go:
| Phase | Status | Notes |
|---|---|---|
| 1. Core | ⬜ | |
| 2. Hot Cache | ⬜ | |
| 3. Graph | ⬜ | |
| 4-5. Trust | ⬜ | |
| 6. Sessions | ⬜ | |
| 7. Mining | ⬜ | |
| 8. Seeding | ⬜ | |
| 9-10. Predictive | ⬜ | |
| 11. Maintenance | ⬜ | |
| 12. Resources | ⬜ | |
| 14. Edge Cases | ⬜ | |
| 15. Cleanup | ⬜ |
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.
- 3d ago First seen · 75 lines · 9 tokens per session scan A 689bac36af87
test-all is a command published in the GitHub repository michael-denyer/memory-mcp (7 stars, last pushed 15d ago), licensed MIT. It adds 9 tokens to every session and 732 once invoked, about $0.0000 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.
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.
neo-review
Get Neo's code review with semantic matching against past findings in memory. Use on a diff or module before merge, especially where earlier mistakes in this codebase are likely to recur. Skip for formatting, lint-catchable issues, and single-line changes.