What is 002_memory_commands?

A command guide for manually saving, checking, initializing, and managing project information in an Enhanced Memory Bank.

Use commands such as /memory init, /memory status, /memory help, and /memory save to set up the system, inspect it, learn its options, or save context.

It gives developers a consistent way to control stored project context instead of relying on memory or undocumented steps.

002_memory_commands — Cursor rule for Cursor by forsonny

Install

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.

Clone the repo

git clone --depth 1 https://github.com/forsonny/Enhanced-Cursor-Memory-Bank-System

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/forsonny/enhanced-cursor-memory-bank-system/002_memory_commands/github.svg)](https://agentmods.dev/rules/forsonny/enhanced-cursor-memory-bank-system/002_memory_commands)

Your own site

<a href="https://agentmods.dev/rules/forsonny/enhanced-cursor-memory-bank-system/002_memory_commands"><img src="https://agentmods.dev/badge/rules/forsonny/enhanced-cursor-memory-bank-system/002_memory_commands/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/forsonny/enhanced-cursor-memory-bank-system/002_memory_commands"><img src="https://agentmods.dev/badge/rules/forsonny/enhanced-cursor-memory-bank-system/002_memory_commands.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 2,804 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.02804
Opus 5.5	$0.00000	$0.01122
Sonnet 5.5	$0.00000	$0.00561
Haiku 4.5	$0.00000	$0.00280

Measured 2mo ago against content hash 614d1709e011, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

002_memory_commands 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 2mo 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.

example/cursor/rules/002_memory_commands.mdc · 340 lines

How it starts

The opening of the file, as written. The whole thing — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Memory Commands

This rule defines the command interface for directly interacting with the memory system. These commands provide explicit control over memory operations, adapted for Cursor's environment.

Command Syntax

All memory commands use the /memory prefix followed by the specific operation:

/memory <command> [arguments]

Available Commands

Core Commands

/memory init - Initialize the memory system for a new project
- Checks if memory files and structure exist
- Provides instructions for creating necessary files if they don't exist
- Guides through initial setup process
/memory status - Display current memory system status
- Shows configuration information
- Lists available memory files
- Reports current mode
- Indicates initialization status
/memory help - Show available memory commands and usage
- Displays command list with descriptions
- Provides examples of common usage

Memory Management

/memory save <context> - Save current information to specified memory context
- Example: /memory save architecture to update architecture memory
- Options: Add -t flag for temporary (short-term) storage
- Implementation: Provides text for the user to add to the specified memory file
/memory recall <context> - Retrieve information from specified memory context
- Example: /memory recall patterns to view established patterns
- Options: Add -v flag for verbose output with metadata
- Implementation: Requests user to open specified file and then reads its content
/memory update <file> <content> - Update specific memory file
- Example: /memory update decisions.md "Decision: We will use TypeScript for all new code"
- Implementation: Provides formatted text for the user to add to the specified file
/memory search <query> - Search across memory for relevant information
- Example: /memory search authentication
- Options: Add -c <context> to limit search to specific memory context
- Implementation: Requests user to open relevant files, then searches their content

Read the full file on GitHub · 340 lines

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.

2mo ago First seen · 340 lines · 2,804 tokens per session scan A 614d1709e011

Subscribe to this mod's changes

002_memory_commands is a cursor rule published in the GitHub repository forsonny/Enhanced-Cursor-Memory-Bank-System (36 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,804 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.

LLM Memory and context cursor vibe-coding

002_memory_commands next to 6 cursor rules from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
002_memory_commandsforsonny/Enhanced-Cursor-Memory-Bank-System	Cursor rule	36	1y ago	MIT	A	0	Cursor
compression-safetyyvgude/lean-ctx	Cursor rule	3.9k	yesterday	Apache-2.0	A	399	Cursor
honcho_rulesmatthewdcage/llm-swarm-router	Cursor rule	26	7d ago	MIT	A	1,412	Cursor
nauro-adoptNauro-AI/nauro	Cursor rule	11	2d ago	Apache-2.0	A	89	Cursor
nauro-contextNauro-AI/nauro	Cursor rule	11	2d ago	Apache-2.0	A	272	Cursor
compendiumhocestnonsatis/Compendium	Cursor rule	0	4d ago	MIT	A	564	Cursor
memforge-auto-recallzql0805/memforge	Cursor rule	2	4mo ago	MIT	A	7,463	Cursor