vectorize-io/hindsight is an agent memory system that stores experiences and helps AI agents learn over time instead of only recalling conversation history. It is used by developers adding long-term memory to agents, including coding agents. Catalogue add-ons connect agents to Hindsight and its memory workflows.
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/vectorize-io/hindsightWrote 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/vectorize-io/hindsight/hindsight-memory)<a href="https://agentmods.dev/rules/vectorize-io/hindsight/hindsight-memory"><img src="https://agentmods.dev/badge/rules/vectorize-io/hindsight/hindsight-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/vectorize-io/hindsight/hindsight-memory"><img src="https://agentmods.dev/badge/rules/vectorize-io/hindsight/hindsight-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.00304 | $0.00304 |
| Opus 5.5 | $0.00122 | $0.00122 |
| Sonnet 5.5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
hindsight-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.
What it actually says
You have access to Hindsight long-term memory through the Hindsight plugin.
Automatic behavior (no action needed):
- Session memory — at the start of each session, the plugin recalls relevant project memories. Recalled memories appear inside a
<hindsight_memories>block in.cursor/rules/hindsight-session.mdc(a file generated by the plugin; safe to delete, will be regenerated). Use those memories to inform your responses. - Auto-retain — after each task, the plugin stores the conversation transcript to Hindsight for future recall. No action needed from you.
On-demand memory tools (via MCP):
- Use the Hindsight MCP tools (
recall,retain,reflect) when the user asks about past decisions, preferences, or project context that isn't covered by the automatic session memory. - Use
recallto search for specific memories beyond what was injected at session start. - Use
retainto explicitly store important decisions or context that should persist. - Use
reflectto reason over accumulated memories when making architectural or design decisions.
Guidelines:
- When memories conflict with current context, prefer current context and note the discrepancy.
- Do not expose raw memory metadata to the user unless asked.
- Prioritize recalled memories that are directly relevant to the current task. Ignore memories that are not applicable.
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 · 22 lines · 304 tokens per session scan A f6498ac79c58
hindsight-memory is a cursor rule published in the GitHub repository vectorize-io/hindsight (50,509 stars, last pushed today), licensed MIT. It adds 304 tokens to every session, about $0.0012 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
pi-en
PI Cognitive AI. Trigger: $pi/coding/dev/code/architecture/API/refactor/debug/bug/error/exception/crash/timeout/performance/optimization/test/compile/git/release/verify/review/CR/product/requirements/ops/growth/design/team/support, or deep/2+ failures/looping/stuck/giving-up/retry/nevermind.
pi
A set of Chinese-language rules for an agent that treats the user as a collaborative partner. It requires checking information before acting, verifying changes, showing evidence, and keeping responses focused.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.