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/forsonny/Enhanced-Cursor-Memory-Bank-SystemWrote 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/forsonny/enhanced-cursor-memory-bank-system/005_memory_events)<a href="https://agentmods.dev/rules/forsonny/enhanced-cursor-memory-bank-system/005_memory_events"><img src="https://agentmods.dev/badge/rules/forsonny/enhanced-cursor-memory-bank-system/005_memory_events.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.00000 | $0.01763 |
| Opus 5 | $0.00000 | $0.00881 |
| Sonnet 5 | $0.00000 | $0.00353 |
| Haiku 4.5 | $0.00000 | $0.00176 |
Grade A, and why
005_memory_events 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.
How it starts
The opening of the file, as written. The whole thing — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Events System
This rule defines how I should respond to user-reported development events and suggest appropriate memory updates based on these events.
Event Reporting
Since automatic event detection isn't possible within Cursor's environment, I rely on users to report significant events using:
/memory event <event_type> <description>
For example:
/memory event commit "Implemented user authentication flow"
Supported Event Types
I recognize and respond to these event types:
File Events
| Event Type | Description | Example |
|---|---|---|
create |
New file added | /memory event create "Created auth middleware" |
modify |
File modified | /memory event modify "Updated login component" |
delete |
File removed | /memory event delete "Removed legacy auth" |
Build Events
| Event Type | Description | Example |
|---|---|---|
build_success |
Build completed successfully | /memory event build_success "All tests passing" |
build_failure |
Build failed | /memory event build_failure "Auth module failing" |
Test Events
| Event Type | Description | Example |
|---|---|---|
test_success |
Tests passed | /memory event test_success "Auth tests passing" |
test_failure |
Tests failed | /memory event test_failure "Login tests failing" |
Git Events
| Event Type | Description | Example |
|---|---|---|
commit |
Code committed | /memory event commit "Implemented authentication" |
branch |
Branch changed | /memory event branch "Switched to feature/auth" |
merge |
Branches merged | /memory event merge "Merged auth branch to main" |
Session Events
| Event Type | Description | Example |
|---|---|---|
session_start |
Beginning development session | /memory event session_start "Starting auth work" |
session_end |
Ending development session | /memory event session_end "Completed login feature" |
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 · 254 lines · 1,763 tokens per session scan A acdb2907b993
005_memory_events 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 1,763 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.
Other cursor rules, from other repositories
compression-safety
Cursor rule "compression-safety" from yvgude/lean-ctx, covering compression safety — prevent lean-ctx marker corruption, the problem, rules for all agents, never write compressed content to files and file restoration commands.
honcho_rules
Honcho persistent memory — capture every conversation, recall past context, and build a growing model of the user. Activates on every conversation.
nauro-adopt
Seeds Nauro's project store from an existing repo. Use after nauro adopt has run locally. On filesystem-capable surfaces, reads docs (README, manifests, ADRs, Memory-Bank) for rationale and inspects code, config, tests, lockfiles, and recent git history for evidence, then surfaces targeted probes that turn evidence…
nauro-context
Writes durable shared context into Nauro's project store so other agents (a later session or a parallel one) can discover and pull it, finds and reads context another agent left, or captures a resumable brief so your own next session in this environment picks up cleanly. Three modes. Author writes a shared brief for…
memforge-auto-recall
Rules that make an AI assistant automatically retrieve and save team memories during conversations.
compendium
Prefer the Compendium MCP gateway to shrink noisy/large context before pasting it into the conversation.