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.
npx skills add vectorize-io/hindsight --skill hindsight-cloudgit 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/skills/vectorize-io/hindsight/hindsight-cloud)<a href="https://agentmods.dev/skills/vectorize-io/hindsight/hindsight-cloud"><img src="https://agentmods.dev/badge/skills/vectorize-io/hindsight/hindsight-cloud/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/skills/vectorize-io/hindsight/hindsight-cloud"><img src="https://agentmods.dev/badge/skills/vectorize-io/hindsight/hindsight-cloud.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Supply Chain · line 24 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
- high Tool Misuse · line 24 Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
- medium Rogue Agent · line 27 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Privilege Escalation · line 34 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00039 | $0.01478 |
| Opus 5.5 | $0.00016 | $0.00591 |
| Sonnet 5.5 | $0.00008 | $0.00296 |
| Haiku 4.5 | $0.00004 | $0.00148 |
Grade D, and why
hindsight-cloud scanned grade D with 3 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 2mo 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 600 ~/.hindsight/config Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://hindsight.vectorize.io/get-cli | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://hindsight.vectorize.io/get-cli | bash Copies of this mod
3 near-identical copies found in the catalogue:
- hindsight-cloud — 100% identical, 0 lines differ
- hindsight-self-hosted — 94% identical, 17 lines differ
- hindsight-self-hosted — 94% identical, 17 lines differ
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hindsight Memory Skill (Cloud)
You have persistent memory via Hindsight Cloud. This memory bank is shared with the team, so knowledge stored here benefits everyone working on this codebase.
Proactively store team knowledge and recall context to provide better assistance.
Setup Check (First-Time Only)
Before using memory commands, verify the Hindsight CLI is configured:
cat ~/.hindsight/config
If the file doesn't exist or is missing credentials, help the user set it up:
-
Install the CLI (if
hindsightcommand not found):curl -fsSL https://hindsight.vectorize.io/get-cli | bash -
Create the config file - ask the user for their API Key (get it from https://ui.hindsight.vectorize.io):
mkdir -p ~/.hindsight cat > ~/.hindsight/config << 'EOF' api_url = "https://api.hindsight.vectorize.io" api_key = "<user's API key>" EOF chmod 600 ~/.hindsight/config -
Get the bank ID - ask the user for their team's bank ID (e.g.,
team-myproject)
After setup, use the bank ID in all commands below.
How Hindsight Works
When you call retain, Hindsight does not store the string as-is. The server runs an internal pipeline that:
- Extracts structured facts from the content using an LLM
- Identifies entities (people, tools, concepts) and links related facts
- Builds temporal and causal relationships between facts
- Generates embeddings for semantic search
This means you should pass rich, full-context content — the server is better at extracting what matters than a pre-summarized string. Your job is to decide when to store, not what to extract.
Commands
Replace <bank-id> with the user's actual bank ID (e.g., team-frontend).
Store a memory
Use memory retain to store what you learn. Pass full context — raw observations, session notes, or detailed descriptions:
hindsight memory retain <bank-id> "The project uses ESLint configured with the Airbnb rule set and Prettier for formatting. Auto-fix on save is enabled in the editor config."
hindsight memory retain <bank-id> "Ran the test suite with NODE_ENV=test. Tests pass. Without NODE_ENV=test, the suite fails with a missing config error." --context procedures
hindsight memory retain <bank-id> "Build failed on Node 18 with error 'ERR_UNSUPPORTED_ESM_URL_SCHEME'. Switched to Node 20 and build succeeded." --context learnings
hindsight memory retain <bank-id> "Alice reviewed the PR and asked for verbose commit messages that explain the motivation, not just what changed." --context preferences
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.
- 2mo ago First seen · 150 lines · 39 tokens per session scan D 9c5238859de5
hindsight-cloud is a skill published in the GitHub repository vectorize-io/hindsight (56,207 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,478 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it D with 3 findings (asks for root, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
persistent-notes
Save notes locally to /mnt/workspace/notes.json file. Use when user wants to "save a note" or "remember something".
session-summaries
What the chat right-panel session summary shows, what it costs, and how to make a session summarize well. Load when the user asks about the session summary panel, why a summary looks wrong or empty, or how to turn it on.
semantix
Install and use the semantix memory kernel as a middleware in your agent: extract user preferences / workflows / experience from past sessions, retrieve and inject them on demand. One binary + your agent's own tools.
search-shared-sessions
Search an Agent Relay workspace's shared coding-agent sessions for prior work, decisions, fixes, or the context behind a task or pull request. Use when team history could answer the user's question or prevent repeating an investigation.
memory-audit-belief-duel
A guided review process for conflicting beliefs or memories. It examines cases where two conclusions cannot both be true, including conflicts between a general rule and a more specific memory.
memory-audit-discoverability
A review guide for checking whether stored memories can be found at the right time. It focuses on where memories are attached, when they are triggered, whether aliases are missing, and whether a parent has too many children.