agentmods.dev

setup-memory

An automated setup and upgrade workflow for ClaudeMemory. It checks the installed package, database, configuration, and health before choosing whether to install, upgrade, or verify the system.

In plain words
What is it for?
Use it to install or upgrade ClaudeMemory, run its doctor check and smoke tests, add version markers, and receive restart or usage guidance.
Why use it?
It removes the need to manually determine what setup steps are required. Health checks and smoke tests help confirm that the memory system works afterward.

Skill for Claude CodeCodex

24 1mo ago A scan 12 tokens original MIT
View the source file codenamev/claude_memory
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/codenamev/claude_memory/setup-memory
Any agent
npx skills add codenamev/claude_memory --skill setup-memory
Clone the repo
git clone --depth 1 https://github.com/codenamev/claude_memory

Made for: Claude Code, Codex.

Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,174 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.01174
Opus 5 $0.00006 $0.00587
Sonnet 5 $0.00002 $0.00235
Haiku 4.5 $0.00001 $0.00117

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

Security

Grade A, and why

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

skills/setup-memory/SKILL.md · 175 lines

How it starts

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

ClaudeMemory Setup & Upgrade

This skill automatically sets up or upgrades ClaudeMemory based on your current state.

What This Skill Does

When invoked, it will:

  1. Check current installation status

    • Detect installed gem version
    • Check database existence and health
    • Verify configuration files

  2. Determine required action

    • Fresh install (no databases)
    • Upgrade (version mismatch)
    • Verification (already up to date)

  3. Execute setup/upgrade automatically

    • Run claude-memory doctor for health check
    • Add version markers to .claude/CLAUDE.md
    • Run smoke tests
    • Report results

  4. Provide next steps

    • Restart recommendations if needed
    • Usage guidance

Instructions

IMPORTANT: This skill should take action, not just provide instructions.

Step 1: Check Installation Status

gem list claude_memory
claude-memory --version
claude-memory doctor

Analyze the output to determine current state.

  • If gem list shows no claude_memory entry, the gem is not installed. Guide the user: gem install claude_memory
  • If running in plugin mode (CLAUDE_PLUGIN_ROOT is set), hooks and MCP are managed by the plugin — only databases and memory instructions need setup.

Step 2: Determine Action Required

  • Not installed: Databases don't exist
    • Action: Run claude-memory init (ask user for --global flag preference)
  • Installed but outdated: Version marker missing or old
    • Action: Run upgrade steps (doctor, add version marker, verify)
  • Up to date: All healthy
    • Action: Report status only

Step 3: Execute Required Actions

For Fresh Install:

  1. Ask user: "Install globally only or with project memory? [project/global]"
  2. Run claude-memory init (with --global if selected)
  3. Run claude-memory doctor to verify
  4. Add version marker to .claude/CLAUDE.md
  5. Report success

For Upgrade:

  1. Run claude-memory doctor (auto-runs migrations)
  2. Add/update version marker in .claude/CLAUDE.md
  3. Run claude-memory stats for smoke test
  4. Report upgrade complete

Read the full file on GitHub · 175 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. 2d ago First seen · 175 lines · 12 tokens per session scan A e7eba2ba7b5a

Subscribe to this mod's changes

setup-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 1,174 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.

DatabasesMemory and contextTesting
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

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…

vercel/next.js · 95 tokens

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…

openai/codex · 114 tokens

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…

openai/codex · 113 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

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…

vercel/next.js · 170 tokens