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/e-gov/cursor-promptsWrote 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/e-gov/cursor-prompts/agent-memory)<a href="https://agentmods.dev/rules/e-gov/cursor-prompts/agent-memory"><img src="https://agentmods.dev/badge/rules/e-gov/cursor-prompts/agent-memory/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/e-gov/cursor-prompts/agent-memory"><img src="https://agentmods.dev/badge/rules/e-gov/cursor-prompts/agent-memory.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.00450 | $0.00450 |
| Opus 5.5 | $0.00180 | $0.00180 |
| Sonnet 5.5 | $0.00090 | $0.00090 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
agent-memory 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 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.
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
Must consult existing memory
MUST DO WITH EACH REQUEST
- First action for each chat request should be to read @agent-memory.md
- Last action for each chat should be to update @agent-memory.md if needed.
Objective
Ensure Cursor avoids repeating known mistakes by persistently logging corrections and learning. All requests must reference stored knowledge in:
docs/agent-memory.md— for known mistakes and their fixes
Rule: Learn from Mistakes
On Every mistake or deprecation warning
-
Detect incorrect or suboptimal outputs.
-
Correct the mistake.
-
Save both mistake and correction in @agent-memory.md using the format:
### Mistake: [Short Description] **Wrong**: [Insert incorrect code or logic] **Correct**: [Insert corrected code or logic]
Always add a step to read @agent-memory.md in your thoughts
Rule: Prevent Repetition
On Every Request
- Always read @agent-memory.md before applying logic.
- If a related mistake is found:
- Use the corrected approach instead.
- Log that a prior fix was applied (optional debug).
Rule: Keep Memory Clean and Updated
- If a better fix is found for an existing issue:
- Update that section in @agent-memory.md.
- Structure the memory files with clear
###headers. - Group by topic if needed.
- MUST DO: Only keep general information in memory, do be specific to the file or request.
- MUST DO: Avoid storing one-off, file-specific details that are unlikely to be reusable.
- MUST DO: Information saved in memory should be useful and reusable.
Storage Paths
docs/agent-memory.md: Persistent log of mistakes and their fixes
Enforcement
- Failing to read or update memory files after a mistake is a critical error.
- All requests must use and comply with stored knowledge.
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 · 75 lines · 450 tokens per session scan A d39072e065cd
agent-memory is a cursor rule published in the GitHub repository e-gov/cursor-prompts (34 stars, last pushed 6mo ago), licensed MIT. It adds 450 tokens to every session, about $0.0018 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-08-30.
Other cursor rules, from other repositories
mempalace-recall-always
Always-on MemPalace recall — search the palace before answering about past work, people, projects, or prior decisions.
dreamd-recall
Recall lessons, decisions, and prior context from the .agent/ memory daemon. Use when starting work in a project that has a .agent/ folder, when the user references a past decision, or when you are about to make a choice that has a documented prior.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.
common_memory_bank
I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read…
self-improving-obsidian-llm-wiki
LLM Wiki OS operating rules.
memsprout
Cursor rule "memsprout" from memsprout/agents, covering using memsprout, search first, capturing, spaces and topics and files.