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/checkgit 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.00486 |
| Opus 5 | $0.00000 | $0.00243 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
check 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.
What it actually says
/check -- Quick Health Check
Run a quick scan of the memory system's health. For daily use.
Usage
/check-- Scan everything (default)/check memory-- Only check memory files (capacity, orphans, broken links)/check commands-- Only check command files (duplicates, broken paths)/check hooks-- Only check hook scripts (exist, readable, configured)/check {project}-- Only check a specific project's memory files
What It Checks (Full Scan)
1. Memory File Structure
- Does each memory file exist and is it readable?
- Are index entries in MEMORY.md pointing to real files?
2. MEMORY.md Capacity
- Line count vs. 200-line system limit
- Below 170 = safe, 170-200 = warning, above 200 = danger (content truncated)
3. Duplicate Content
- Same rule or fact appearing in multiple files
- Identify the "single source of truth" for each piece of information
4. Size Check
- Memory files over 200 lines -> suggest splitting
- Reference files over 300 lines -> suggest splitting
5. Orphan Check
- Memory files not indexed by MEMORY.md (orphans)
- MEMORY.md entries pointing to non-existent files (broken links)
6. Environment Status
- CLAUDE.md: exists and readable?
- MEMORY.md: line count and capacity
- commands/: how many commands
- skills/learned/: how many skills
- memory/: how many memory files
Output Format
=== Quick Health Check ===
Environment:
- CLAUDE.md: OK ({N} lines)
- MEMORY.md: OK/WARNING ({N}/200 lines)
- commands/: {N} commands
- skills/learned/: {N} skills
- memory/: {N} files
Index:
- [OK] All MEMORY.md entries point to existing files
- [BROKEN] {entry} points to non-existent {file}
Size:
- [OK] All files within limits
- [WARNING] {file} has {N} lines, suggest splitting
Suggestions:
1. ...
2. ...
Notes
- List suggestions but do NOT auto-modify any files
- Wait for user confirmation before making 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.
- 2d ago First seen · 71 lines · 0 tokens per session scan A acd66ddadc00
check 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 486 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
design-review
Workflow recipe — review a design end-to-end, ending in measured numbers rather than adjectives, by chaining 4 skills.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
validate-dependencies
Validate all task dependencies for issues.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.