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.
git clone --depth 1 https://github.com/HelloRuru/claude-memory-engineWrote 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.
[](https://agentmods.dev/commands/helloruru/claude-memory-engine/backup)<a href="https://agentmods.dev/commands/helloruru/claude-memory-engine/backup"><img src="https://agentmods.dev/badge/commands/helloruru/claude-memory-engine/backup/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.
<a href="https://agentmods.dev/commands/helloruru/claude-memory-engine/backup"><img src="https://agentmods.dev/badge/commands/helloruru/claude-memory-engine/backup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00183 |
| Opus 5.5 | $0.00000 | $0.00073 |
| Sonnet 5.5 | $0.00000 | $0.00037 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade B, and why
backup scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
1. **Scan all projects** -- find every `~/.claude/projects/*/memory/` directory What it actually says
/backup -- Push Memory to GitHub
Push local memory files to your GitHub backup repository.
Usage
bash ~/.claude/scripts/hooks/memory-backup.sh push
What it does
- Scan all projects -- find every
~/.claude/projects/*/memory/directory - Copy to backup repo -- mirror all
.mdfiles into the backup repo - Commit -- stage and commit changes
- Push -- push to GitHub
Notes
- The SessionEnd hook auto-commits locally after every conversation; this command handles the push
- v1.6: push now auto-detects all project directories instead of hardcoding paths
- For bidirectional sync (push + pull), use
/syncinstead - For pulling from GitHub, use
/recover
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.
- 1mo ago First seen · 24 lines · 0 tokens per session scan B 331483b63e06
backup is a command published in the GitHub repository HelloRuru/claude-memory-engine (134 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 183 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
brain-team-setup
Initialize or update team vault settings — git-backed shared knowledge vault.
context-stats
Display context window usage and token statistics.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
deploy
Deploy application with pre/post-deploy checks.
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.
git-ops
Git + worktree orchestrator entry point. /git-ops --landall surveys every branch/worktree and batch-lands the ones that are done; bare /git-ops runs a status survey. Thin router over the git-ops skill.