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.
npx agentmods add rules/miguelmedeiros/unforgit/unforgit-memorygit clone --depth 1 https://github.com/MiguelMedeiros/unforgitWhat 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 | $0.00426 | $0.00426 |
| Opus 5 | $0.00213 | $0.00213 |
| Sonnet 5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
unforgit-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 2d 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
Unforgit Memory Integration
You have access to unforgit_recall and unforgit_add MCP tools for persistent repository memory across sessions.
1. Recall at the Start
At the beginning of every conversation, use the unforgit_recall tool with a query based on the user's first message to retrieve relevant context from past sessions.
Use recalled memories to avoid repeating past mistakes, follow known conventions, and apply previous decisions.
2. Save During the Conversation
Save memories as soon as something noteworthy happens — don't wait until the end.
Trigger a save with the unforgit_add tool immediately after:
- A bug is found and fixed
- An architectural or design decision is made
- A non-obvious gotcha or workaround is discovered
- A new convention or pattern is established
- A deployment/setup procedure is figured out
Memory types
| Type | When | Example |
|---|---|---|
semantic |
Decisions, conventions, architecture facts | "We use UTC timestamps everywhere" |
procedural |
Workflows, how-tos, playbooks | "To deploy: run make release, then kubectl apply" |
episodic |
Bugs found, gotchas, observations | "Found race condition in queue worker" |
Rules
- Keep text concise but self-contained — a future reader should understand it without extra context
- Use meaningful tags for discoverability (e.g.
["auth", "bug"],["deploy", "playbook"]) - Prefer
semanticfor stable facts,proceduralfor how-tos,episodicfor transient observations - Do NOT save trivial changes, obvious things, or info already in the codebase docs
- Quality over quantity — only save what's genuinely useful for future sessions
- Always write memory text in English, regardless of the language the user is speaking
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.
- 2d ago First seen · 43 lines · 426 tokens per session scan A 42a224a90b12
unforgit-memory is a cursor rule published in the GitHub repository MiguelMedeiros/unforgit (9 stars, last pushed 2d ago), licensed MIT. It adds 426 tokens to every session, about $0.0021 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-31.
Other cursor rules, from other repositories
cursorrules
You are an expert software engineer and architect. You are part of a team, but your memory is reset after every session. To compensate for this, you rely on a "Memory Bank" stored in the memory/ directory.
svg-check
Apply when editing, generating, or reviewing any SVG diagram. Pixel-perfect Playwright bbox-check is the acceptance test — eyeballing is not sufficient. Run on every SVG before declaring done.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.