test-memory

test-memory is a skill for Claude Code, Codex from michael-denyer/memory-mcp. It costs 12 tokens per session (3,553 once invoked), scanned A, original, MIT.

An interactive test guide for all features of the Memory MCP system. MCP is a way for an AI assistant to call external tools, and this guide walks through live memory tests.

In plain words
What is it for?
Use it to install the memory plugin and test memory storage, meaning-based recall, recall modes, confidence results, and other listed Memory MCP features.
Why use it?
It provides a repeatable sequence for checking whether storing, finding, and evaluating memories work as expected.

Skill for Claude CodeCodex

Part of the memory-mcp plugin — 3 skills, 14 commands, 1 agent, 1 MCP server shipped together

Install

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.

agentmods
npx agentmods add skills/michael-denyer/memory-mcp/test-memory
Any agent
npx skills add michael-denyer/memory-mcp --skill test-memory
Clone the repo
git clone --depth 1 https://github.com/michael-denyer/memory-mcp

Made for: Claude Code, Codex.

Or install memory-mcp, the plugin that ships this one along with the rest of its 3 skills, 14 commands, 1 agent, 1 MCP server.

Wrote 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.

agentmods badge for test-memory

README.md
[![agentmods](https://agentmods.dev/badge/skills/michael-denyer/memory-mcp/test-memory.svg)](https://agentmods.dev/skills/michael-denyer/memory-mcp/test-memory)
Your own site
<a href="https://agentmods.dev/skills/michael-denyer/memory-mcp/test-memory"><img src="https://agentmods.dev/badge/skills/michael-denyer/memory-mcp/test-memory.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,553 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.03553
Opus 5 $0.00006 $0.01776
Sonnet 5 $0.00002 $0.00711
Haiku 4.5 $0.00001 $0.00355

Measured 3d ago against content hash 7dbb3c8d4ccc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test-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 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.

.claude/skills/test-memory/SKILL.md · 440 lines

How it starts

The opening of the file, as written. The whole thing — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Memory MCP Live Testing Skill

Run /test-memory to start a guided testing session. Walk through each phase, execute tests, and track results.

Prerequisites

Install memory-mcp from the marketplace:

# Add the marketplace
/plugin marketplace add michael-denyer/memory-mcp

# Install the plugin
/plugin install memory-mcp@michael-denyer/memory-mcp

Or install directly:

/plugin install github:michael-denyer/memory-mcp

Phases


Phase 1: Core Memory Operations

1.1 Remember - Store test memories:

remember("Test: FastAPI with async endpoints", memory_type="project", tags=["test", "tech-stack"])
remember("Test: Always use uv run pytest -v", memory_type="pattern", tags=["test", "commands"])
remember("Test: API rate limit 100 req/min", memory_type="reference", tags=["test", "api"])

Record the returned IDs for later tests.

1.2 Recall - Semantic search (use different phrasings):

  • "what framework for backend" → should find FastAPI
  • "how to run tests" → should find pytest
  • "request throttling" → should find rate limit

Verify confidence levels returned.

1.3 Recall Modes - Compare precision vs exploratory:

  • recall("testing", mode="precision") → fewer, higher-confidence
  • recall("testing", mode="exploratory") → more results

1.4 Recall by Tag:

  • recall_by_tag("test") → should return all test memories

1.5 Forget - Delete one test memory and verify it's gone.


Phase 2: Hot Cache Mechanics

2.1 Manual Promotion:

  • promote(memory_id) one of the test memories
  • hot_cache_status() → verify it appears

2.2 Manual Demotion:

  • demote(memory_id)
  • Verify removed from hot cache but still recallable

2.3 Pin/Unpin:

  • pin(memory_id) → pinned_count increases
  • unpin(memory_id) → pinned_count decreases

2.4 Auto-Promotion (optional - requires multiple recalls):

  • Create a memory and recall it 3+ times
  • Check if auto-promoted

Phase 3: Knowledge Graph

3.1 Create Linked Memories:

remember("Test: Database uses PostgreSQL") → ID: A
remember("Test: pgvector for embeddings") → ID: B
remember("Test: Vector search needs pgvector") → ID: C
link_memories(A, B, "relates_to")
link_memories(B, C, "depends_on")

Read the full file on GitHub · 440 lines

Changes

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.

  1. 3d ago First seen · 440 lines · 12 tokens per session scan A 7dbb3c8d4ccc

Subscribe to this mod's changes

test-memory is a skill published in the GitHub repository michael-denyer/memory-mcp (7 stars, last pushed 15d ago), licensed MIT. It adds 12 tokens to every session and 3,553 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens