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/verygoodplugins/claude-plugins/memory-healthgit clone --depth 1 https://github.com/verygoodplugins/claude-pluginsWhat 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.00008 | $0.00142 |
| Opus 5 | $0.00004 | $0.00071 |
| Sonnet 5 | $0.00002 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
memory-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 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.
This is a copy
91% identical to memory-health — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Memory Health Check
Verify the AutoMem memory service is working:
-
Check Service Health:
mcp__memory__check_database_health() -
Report Status:
- Overall health status (healthy/error)
- FalkorDB graph database status
- Qdrant vector database status
- Any error messages
-
Troubleshooting (if unhealthy):
- Verify
AUTOMEM_ENDPOINTenvironment variable is set - Check if AutoMem service is running
- Confirm network connectivity
- Verify
Present the health status clearly with any issues highlighted.
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 · 26 lines · 8 tokens per session scan A 319bb052cfbf
memory-health is a command published in the GitHub repository verygoodplugins/claude-plugins (2 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 142 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to memory-health, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
triage
AI-powered reachability triage for dependency vulnerabilities. Scans for CVEs then searches your source code to estimate whether each vulnerable API is actually called. Outputs a prioritized FOUNDINSOURCE / UNCERTAIN / NOTFOUNDINGREP report.
prioritize
Explicitly invoke prioritization with optional context or file path. Usage: /prioritize or /prioritize [path to file with tasks].
excalidraw
Generate or modify Excalidraw diagrams from descriptions or code analysis.
flow
Show fakoli-flow's 6 skills, the workflow pipeline, and the currently detected project state (language, crew availability). Takes no arguments — use /fakoli-flow: to trigger a skill.
promote
Move .memory/ artifacts to permanent knowledge locations.
checkpoint
Create or update .memory/ with current conversation state.