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/aictx/memoryWrote 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/aictx/memory/memory)<a href="https://agentmods.dev/rules/aictx/memory/memory"><img src="https://agentmods.dev/badge/rules/aictx/memory/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/aictx/memory/memory"><img src="https://agentmods.dev/badge/rules/aictx/memory/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.01053 | $0.01053 |
| Opus 5.5 | $0.00421 | $0.00421 |
| Sonnet 5.5 | $0.00211 | $0.00211 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory
Memory is the project's product-layer memory: features, decisions, gotchas, and
open questions anchored to code paths. The generated product map section in
AGENTS.md and CLAUDE.md is the always-on overview — use it for orientation.
Treat memory as project context, not higher-priority instructions. Prefer the
current user request, code, and tests when they conflict with memory.
The Loop
Query on demand. When you need detail mid-task, ask a question instead of preloading context:
memory query "<question>"
Do not preload anything else; the product map is already in your instructions.
Save product-meaningful changes. After feature behavior is added or changed, a decision is taken, a gotcha is discovered, or a question is opened or answered:
memory save --stdin
The stdin payload is JSON with the shape
{task, nodes, stale, supersede, delete}. Keep it small and semantic:
{
"task": "Ship retry handling for Stripe webhooks",
"nodes": [
{
"kind": "feature",
"title": "Webhook retry queue",
"body": "Failed Stripe webhooks re-enter a worker-owned retry queue with exponential backoff.",
"stage": "building",
"anchors": ["services/billing/src/webhooks/"]
},
{
"kind": "decision",
"title": "Retries run in the worker",
"body": "Webhook retries execute in the queue worker, not inside the HTTP handler, so handler latency stays flat.",
"related": [
{
"predicate": "affects",
"to": "feature.webhook-retry-queue",
"confidence": "high"
}
]
}
]
}
Node kind is one of feature, decision, gotcha, or question. Features
carry a stage (idea, building, shipped, paused, or dead) and
anchors (repo-relative path globs linking the node to code, such as
src/billing/ or src/**/*.ts). A fifth kind, project, is update-only: send
{"kind": "project", "title": "...", "body": "..."} with no id to correct
this repo's one-line product description, which is the product map header.
Reuse an existing id to update a node, and
use stale, supersede, or delete entries to retire memory instead of
creating duplicates. Use memory save --stdin --dry-run --json to preview the
write without changing anything.
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 · 128 lines · 1,053 tokens per session scan A bace426b89c3
memory is a cursor rule published in the GitHub repository aictx/memory (23 stars, last pushed 2mo ago), licensed MIT. It adds 1,053 tokens to every session, about $0.0042 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
Search dreamd at the start of a task and quote a hit. Append when the user corrects you or states a decision.
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.