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/rules/verygoodplugins/mcp-automem/automem)<a href="https://agentmods.dev/rules/verygoodplugins/mcp-automem/automem"><img src="https://agentmods.dev/badge/rules/verygoodplugins/mcp-automem/automem/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/rules/verygoodplugins/mcp-automem/automem"><img src="https://agentmods.dev/badge/rules/verygoodplugins/mcp-automem/automem.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.02201 | $0.02201 |
| Opus 5.5 | $0.00880 | $0.00880 |
| Sonnet 5.5 | $0.00440 | $0.00440 |
| Haiku 4.5 | $0.00220 | $0.00220 |
Grade A, and why
automem 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AutoMem Memory Integration
Use AutoMem proactively to maintain persistent context across sessions for the current workspace. Preserve host/platform instructions; this rule ships with the AutoMem plugin and applies to every workspace. The project slug is the workspace folder name, lowercased with hyphens (written as <workspace-folder-slug> below); the plugin's session-start hook derives it for you.
Cursor MCP server: memory. Discover its tools before the first call and use the live tool inventory. Cursor may expose server-local tool names through its MCP dispatcher or direct callable names. The examples below use the direct spelling mcp_memory_* (e.g. mcp_memory_recall_memory); when a dispatcher is available, target this server and the corresponding unprefixed tool name instead.
Tool's real behavior (validated against production corpus)
- Tags are a hard gate - memories without matching tags are excluded before scoring. Use tags for stable categories like
preferenceandbugfix; do not guess topic tags. - One good query beats
queries[]+auto_decomposefor focused tasks. Usequeries[]only for genuinely multi-topic questions. limitcaps at 50. Routine recall should use enough budget to be useful.- Default
textformat shows content previews with created/updated timestamps and importance.detailedadds type/confidence/metadata summary. Responses are budget-capped; fetch a full record withrecall_memory({ memory_id }). store_memorycan silently fail. Verify important stores by recalling a distinctive phrase; retry once if missing.- Bare tag convention - Use bare tags only. No namespace prefixes (
project/*,lang/*), no platform tags, and no date-stamped tags. Keep source attribution in metadata and dates in timestamp / t_valid / t_invalid. Useautomem, notproject/automem.entity:*:*tags are server-injected.
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.
- yesterday First seen · 159 lines · 2,201 tokens per session scan A 74b39a459905
automem is a cursor rule published in the GitHub repository verygoodplugins/mcp-automem (66 stars, last pushed today), licensed MIT. It adds 2,201 tokens to every session, about $0.0088 per session on Opus 5.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-11-05.
automem compared with cursor rules from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| automemverygoodplugins/mcp-automem | Cursor rule | 66 | today | MIT | A | 2,201 | Cursor |
| mongodb-memory-server-setupprisma/orm | Cursor rule | 48k | yesterday | Apache-2.0 | A | 28 | Cursor |
| cursor-rulesMatthewSherlin/mushroomdb | Cursor rule | 5 | today | none | A | 1,337 | Cursor |
| ponytailDietrichGebert/ponytail | Cursor rule | 185k | 8d ago | MIT | A | 604 | Cursor |
| angular-20angular/angular | Cursor rule | 101k | yesterday | MIT | A | 0 | Cursor |
| dev-standardapache/superset | Cursor rule | 75k | today | Apache-2.0 | A | 1,147 | Cursor |
| prefer-direct-imports-over-module-mocksprisma/orm | Cursor rule | 48k | yesterday | Apache-2.0 | A | 0 | Cursor |