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/helloruru/claude-memory-engine/memory-healthgit clone --depth 1 https://github.com/HelloRuru/claude-memory-engineWhat 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.00000 | $0.00376 |
| Opus 5 | $0.00000 | $0.00188 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00038 |
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 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.
What it actually says
/memory-health -- Memory Health Check
Check the health status of all memory files and hooks.
Steps
- Scan memory directory:
~/.claude/projects/{project-id}/memory/ - Scan sessions directory:
~/.claude/sessions/ - Scan diary directory:
~/.claude/sessions/diary/ - Scan learned directory:
~/.claude/skills/learned/ - Check debug log:
~/.claude/sessions/debug.log
Output Format
Memory Health Report
MEMORY.md level: {lines}/200 ({percent}%) {Safe/Warning/Critical}
Memory files:
| File | Lines | Last Updated | Status |
|------|-------|-------------|--------|
| {filename} | {lines} | {date} | {OK/Stale/Too Large} |
Sessions: {N} total, latest: {date}
Diary entries: {N} total, latest: {date}
Pitfall records: {N} total, latest: {date}
Learned Skills: {N} total
Hooks status:
- session-start.js: {OK/Error}
- session-end.js: {OK/Error} (debug.log last: {msg})
- memory-sync.js: {OK}
- write-guard.js: {OK}
- pre-push-check.js: {OK}
Thresholds
- MEMORY.md < 170 lines -> Safe
- MEMORY.md 170-200 lines -> Warning, suggest moving content to topic files
- MEMORY.md > 200 lines -> Critical, content beyond line 200 is truncated by Claude
- Memory file not updated for 30+ days -> Stale
- Memory file over 200 lines -> Too Large
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.
- 3d ago First seen · 44 lines · 0 tokens per session scan A 1b78675308c6
memory-health is a command published in the GitHub repository HelloRuru/claude-memory-engine (133 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 376 tokens. 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 commands, from other repositories
build
Run full verification pipeline.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
camera-ready
Convert an accepted anonymous-submission LaTeX paper (AAAI/AIES/ACM-style) to camera-ready and implement the accepted reviews. Use when a paper is accepted with no rebuttal and you need to de-anonymize, add copyright, turn on section numbering, implement each reviewer's minor revisions, optionally move proofs to a…
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
generate-rules
Generate development rules and standards into RULES.md.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.