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 skills/codenamev/claude_memory/check-memorynpx skills add codenamev/claude_memory --skill check-memorygit clone --depth 1 https://github.com/codenamev/claude_memoryWhat 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.00012 | $0.00492 |
| Opus 5 | $0.00006 | $0.00246 |
| Sonnet 5 | $0.00002 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
check-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 2d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Memory First
When invoked with /check-memory <topic>, this skill forces a memory-first workflow.
Task
IMPORTANT: You MUST check memory BEFORE reading any files or running any code searches.
The user is asking about: $ARGUMENTS
Step-by-Step Workflow
0. Verify Memory Health
Before querying, confirm the memory system is operational:
memory.check_setup
If status is not "healthy", inform the user and suggest running claude-memory doctor for details.
1. Query Memory (REQUIRED FIRST STEP)
Run multiple memory queries to find existing knowledge:
memory.recall "$ARGUMENTS"
Also try specialized shortcuts:
memory.decisions(if implementing a feature)memory.architecture(if working with frameworks)memory.conventions(if writing code)memory.conflicts(if encountering contradictions)
2. Analyze Results
Review what memory returns:
- If sufficient: Answer using recalled facts with citations
- If partial: Note what's known and what needs investigation
- If empty: Memory has no knowledge on this topic yet
3. Explore Code (ONLY IF NEEDED)
If memory doesn't have enough information:
- Use Read/Grep/Glob to explore the codebase
- Clearly distinguish between:
- Recalled knowledge (from memory)
- Discovered information (from code exploration)
4. Provide Complete Answer
Combine:
- Facts from memory (with fact IDs if relevant)
- New information from code exploration (if any)
- Clear indication of sources
Example Response Format
Based on memory:
- [Fact from memory with context]
From code exploration:
- [New findings from reading files]
Answer: [Complete response combining both sources]
Why This Matters
Memory contains distilled knowledge from previous sessions. Checking it first:
- Saves time (no need to re-explore known areas)
- Provides context (decisions, patterns, conventions)
- Avoids mistakes (previous lessons learned)
- Reduces token usage (recalled facts are concise)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 88 lines · 12 tokens per session scan A b3e88e70be3a
check-memory is a skill published in the GitHub repository codenamev/claude_memory (24 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 492 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…