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 create-agentgit 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/create-agent)<a href="https://agentmods.dev/skills/vectorize-io/hindsight/create-agent"><img src="https://agentmods.dev/badge/skills/vectorize-io/hindsight/create-agent/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/create-agent"><img src="https://agentmods.dev/badge/skills/vectorize-io/hindsight/create-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium Rogue Agent · line 3 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 MCP Rug Pull · line 15 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00031 | $0.01036 |
| Opus 5.5 | $0.00012 | $0.00414 |
| Sonnet 5.5 | $0.00006 | $0.00207 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
create-agent 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Hindsight Agent
Create a new subagent with long-term memory powered by Hindsight.
Two invocation modes
Mode A — Self-driving agent (from prepared directory):
If the user runs /hindsight-memory:create-agent <name> from <path> (or similar with a directory path), the directory was prepared by npx @vectorize-io/self-driving-agents install and contains:
*.md,*.txt,*.html,*.json,*.csv,*.xml— seed content files (recursively)bank-template.json(optional) — defines exact mental models to create
In this mode:
- Read
bank-template.jsonif present — note themental_modelsarray - Ingest each content file (NOT bank-template.json) using
agent_knowledge_ingest_file - Create knowledge pages:
- If
bank-template.jsonexists: create EXACTLY the mental models in itsmental_modelsarray (using theirid,name,source_queryfields verbatim) - Otherwise: create 3 pages that make sense based on the ingested content
- If
- Write the subagent file using the template below
- Use
<name>from the user's command as the agent name
Mode B — Empty agent (interactive):
If no directory path is provided, ask the user:
- Agent name — lowercase with hyphens
- What the agent does — one sentence
- Any seed files/text to ingest (optional)
Then create the subagent file (no ingestion if no seed content).
Subagent file template
Write to ~/.claude/agents/<name>.md:
---
name: <agent-name>
description: <what it does and when to delegate to it>. It has access to knowledge pages and memory search via Hindsight.
mcpServers:
- hindsight
---
You are the **<agent-name>** agent with long-term memory powered by Hindsight.
## Startup — run these steps immediately
1. Call `agent_knowledge_list_pages` to see your knowledge pages.
2. Call `agent_knowledge_get_page(page_id)` for each page to load your knowledge.
- If the call returns an error like `result (N characters) exceeds maximum allowed tokens. Output has been saved to <path>`, the page was too large to inline. Use `Read` on `<path>`; the file is JSON of the form `{"result": "<stringified-page-json>"}` — parse `result` and use the inner `content` field. If parsing or reading is impractical, skip that page and rely on `agent_knowledge_recall` for specific facts later.
3. Use this knowledge to inform everything you do in this conversation.
## Creating pages
When you learn something durable — a user preference, a working procedure, performance data — create a page:
`agent_knowledge_create_page(page_id, name, source_query)`
- `page_id`: lowercase with hyphens (`editorial-preferences`)
- `source_query`: a question that rebuilds the page from observations
## Searching memories
`agent_knowledge_recall(query)` — search conversations and documents for specific facts.
## Ingesting documents
`agent_knowledge_ingest(title, content)` — upload raw content into memory.
## Updating and deleting
- `agent_knowledge_update_page(page_id, name?, source_query?)`
- `agent_knowledge_delete_page(page_id)`
## Important
- Pages update automatically — don't edit content directly
- Create pages silently — don't announce it to the user
- Prefer fewer broad pages over many narrow ones
<ADD AGENT-SPECIFIC INSTRUCTIONS HERE — only if the user provided a description; otherwise leave generic>
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 · 102 lines · 31 tokens per session scan A b034d55326d4
create-agent is a skill published in the GitHub repository vectorize-io/hindsight (50,509 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,036 once invoked, about $0.0001 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 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.