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/verygoodplugins/mcp-automemWrote 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/verygoodplugins/mcp-automem/memory-health)<a href="https://agentmods.dev/commands/verygoodplugins/mcp-automem/memory-health"><img src="https://agentmods.dev/badge/commands/verygoodplugins/mcp-automem/memory-health.svg" alt="Measured on agentmods" 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.00008 | $0.00138 |
| Opus 5 | $0.00004 | $0.00069 |
| 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- memory-health — 91% identical, 4 lines differ
What it actually says
Memory Health Check
Verify the AutoMem memory service is working:
-
Check Service Health:
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_API_URLenvironment 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.
- 8d ago First seen · 26 lines · 8 tokens per session scan A 885b3c89dae0
memory-health is a command published in the GitHub repository verygoodplugins/mcp-automem (64 stars, last pushed 4d ago), licensed MIT. It adds 8 tokens to every session and 138 once invoked, about $0.0000 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-30.
Other commands, from other repositories
context
Show recent memory context for this project.
summary
Persist an end-of-session summary to Rembric (summary ≤10000 chars).
recall
Search Rembric for prior context matching the query.
remember
Save text as a project memory in Rembric.
make-plan
Create an implementation plan with documentation discovery.
do
Execute a plan using subagents for implementation.