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/syz-coder/superpowers-openspec-team-skills/superpowers-memorygit clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skillsWrote 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/syz-coder/superpowers-openspec-team-skills/superpowers-memory)<a href="https://agentmods.dev/rules/syz-coder/superpowers-openspec-team-skills/superpowers-memory"><img src="https://agentmods.dev/badge/rules/syz-coder/superpowers-openspec-team-skills/superpowers-memory.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 | $0.00263 | $0.00263 |
| Opus 5 | $0.00131 | $0.00131 |
| Sonnet 5 | $0.00053 | $0.00053 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
superpowers-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 4d 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
Superpowers Memory
If .superpowers-memory/ exists in this repository, read it at the start of a new session before asking for project background.
Read in this order:
.superpowers-memory/PROJECT_CONTEXT.md.superpowers-memory/CURRENT_STATE.md.superpowers-memory/DECISIONS.mdwhen it exists.superpowers-memory/KNOWN_FAILURES.mdwhen it exists.superpowers-memory/VERIFICATION_BASELINE.mdwhen it exists.superpowers-memory/TEAM_PREFERENCES.mdwhen it exists.superpowers-memory/USER_PROFILE.mdwhen it exists.superpowers-memory/AGENT_NOTES.mdwhen it exists- The newest files under
.superpowers-memory/session-journal/
When a meaningful Superpowers-related session ends, update CURRENT_STATE.md, any durable files that changed, including USER_PROFILE.md or AGENT_NOTES.md when relevant, and add a short session journal entry.
When memory updates are part of the workflow, run scripts/validate-superpowers-memory.ps1 before claiming completion.
This memory rule does not auto-enable any Superpowers workflow. Workflows still require explicit user opt-in.
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.
- 4d ago First seen · 22 lines · 263 tokens per session scan A 0be06faeb5a8
superpowers-memory is a cursor rule published in the GitHub repository SYZ-Coder/superpowers-openspec-team-skills (191 stars, last pushed 2mo ago), licensed MIT. It adds 263 tokens to every session, about $0.0013 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-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…
memsprout
Cursor rule "memsprout" from memsprout/agents, covering using memsprout, search first, capturing, spaces and topics and files.
self-improving-obsidian-llm-wiki
LLM Wiki OS operating rules.