check-health

check-health is a command for Claude Code from GaZmagik/claude-memory-plugin. It costs 19 tokens per session (2,515 once invoked), scanned A, original, MIT.

A command that checks the health of a memory system across selected scopes. It examines connections between stored items, central index items, metadata fields, and suggested links.

In plain words
What is it for?
Running quick or full health checks for user, project, local, enterprise, or all available memory scopes.
Why use it?
It helps find broken relationships or inconsistent stored information before they make memory searches unreliable.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; names the AskUserQuestion tool.

Part of the claude-memory-plugin plugin — 1 skill, 5 commands, 2 agents, 7 hooks shipped together

Good fit Running quick or full health checks for user, project, local, enterprise, or all available memory scopes.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/gazmagik/claude-memory-plugin/check-health
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.

Clone the repo
git clone --depth 1 https://github.com/GaZmagik/claude-memory-plugin

Made for: Claude Code.

Or install claude-memory-plugin, the plugin that ships this one along with the rest of its 1 skill, 5 commands, 2 agents, 7 hooks.

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 check-health

README.md
[![agentmods](https://agentmods.dev/badge/commands/gazmagik/claude-memory-plugin/check-health/github.svg)](https://agentmods.dev/commands/gazmagik/claude-memory-plugin/check-health)
Your own site
<a href="https://agentmods.dev/commands/gazmagik/claude-memory-plugin/check-health"><img src="https://agentmods.dev/badge/commands/gazmagik/claude-memory-plugin/check-health/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.

agentmods 80×15 button for check-health

Your own site · 80×15
<a href="https://agentmods.dev/commands/gazmagik/claude-memory-plugin/check-health"><img src="https://agentmods.dev/badge/commands/gazmagik/claude-memory-plugin/check-health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,515 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00019 $0.02515
Opus 5 $0.00010 $0.01257
Sonnet 5 $0.00004 $0.00503
Haiku 4.5 $0.00002 $0.00251

Measured 9d ago against content hash 37333c9615c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

check-health 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 9d 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.

commands/check-health.md · 294 lines

How it starts

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

User Input

$ARGUMENTS

Goal

Perform a health check of the memory system using the built-in memory validate command. Supports all 4 scope levels: User, Project, Local, and Enterprise.

Prerequisites

CRITICAL: Before running any memory commands, you MUST activate the memory skill first using the Skill tool:

Skill: memory

This ensures the skill is loaded and the memory CLI command is available (installed via bun link). Without this step, the commands below may not work correctly.

Execution Steps

1. Determine Scope

Check arguments first:

  • --user or --global or user or global → Use user scope
  • --project or project → Use project scope
  • --local or local → Use local scope
  • --enterprise or enterprise → Use enterprise scope (for managed environments)
  • --all or all → Check all accessible scopes sequentially
  • quick or --quick → Quick check mode (can combine with any scope)

Note: --global is accepted as a legacy alias for --user.

If no scope provided, first check which scopes are accessible:

# Check enterprise scope availability (for managed environments)
memory config get scopes.enterprise.enabled 2>/dev/null | jq -r '.data // false'

# Check if in a git repo (for project/local scopes)
git rev-parse --git-dir >/dev/null 2>&1 && echo "in_git_repo"

Then use AskUserQuestion with available options:

{
  "question": "Which memory scope would you like to check?",
  "header": "Memory scope",
  "options": [
    {"label": "User", "description": "Personal cross-project memories in ~/.claude/memory/"},
    {"label": "Project", "description": "Shared project memories in .claude/memory/ (tracked in git)"},
    {"label": "Local", "description": "Personal project memories in .claude/memory/local/ (gitignored)"},
    {"label": "All accessible", "description": "Check all accessible scopes sequentially"}
  ],
  "multiSelect": false
}

Dynamic options:

  • Only show "Project" and "Local" if in a git repository
  • Always show "User" and "All accessible"
  • Enterprise scope is supported but not shown by default (pass --enterprise explicitly)

Read the full file on GitHub · 294 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. 9d ago First seen · 294 lines · 19 tokens per session scan A 37333c9615c4

Subscribe to this mod's changes

check-health is a command published in the GitHub repository GaZmagik/claude-memory-plugin (6 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 2,515 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.