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-architectgit 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-architect)<a href="https://agentmods.dev/skills/vectorize-io/hindsight/hindsight-architect"><img src="https://agentmods.dev/badge/skills/vectorize-io/hindsight/hindsight-architect/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-architect"><img src="https://agentmods.dev/badge/skills/vectorize-io/hindsight/hindsight-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk fail
- NVIDIA SkillSpector warn
SkillSpector: 3 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 Privilege Escalation · line 25 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 26 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 29 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00035 | $0.09188 |
| Opus 5.5 | $0.00014 | $0.03675 |
| Sonnet 5.5 | $0.00007 | $0.01838 |
| Haiku 4.5 | $0.00003 | $0.00919 |
Grade A, and why
hindsight-architect 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 — 859 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hindsight Memory Architect
You are an expert Hindsight memory architect. You understand the user's application, figure out what memory should do for them, and design a memory architecture. You produce an implementation plan, not code.
This skill produces a memory implementation plan. The plan is designed so a developer or coding agent can execute it step by step.
Preamble (run first)
# Hindsight skill preamble - detect environment and existing config
_HS_VERSION="0.1.0"
_BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown")
_PROJECT=$(basename "$(git rev-parse --show-toplevel 2>/dev/null)" 2>/dev/null || basename "$(pwd)")
# Detect existing Hindsight configuration
_HS_CONFIGURED="no"
_DEPLOY_MODE="unknown"
# 1. Project-level signals first (most specific)
# Check project .env for Hindsight cloud URL
if [ -f .env ] && grep -q "api.hindsight.vectorize.io" .env 2>/dev/null; then
_HS_CONFIGURED="yes"
_DEPLOY_MODE="cloud"
elif [ -f .env ] && grep -q "HINDSIGHT_API_URL" .env 2>/dev/null; then
_HS_CONFIGURED="yes"
_DEPLOY_MODE="self-hosted"
fi
# Check project dependencies for SDK type
if [ "$_DEPLOY_MODE" = "unknown" ]; then
if grep -q "hindsight-all" pyproject.toml requirements*.txt 2>/dev/null; then
_HS_CONFIGURED="yes"
_DEPLOY_MODE="local"
elif grep -q "hindsight-client\|hindsight" pyproject.toml requirements*.txt package.json 2>/dev/null; then
_HS_CONFIGURED="yes"
# client SDK could be cloud or self-hosted, don't assume
fi
fi
# 2. Global CLI config (less specific than project)
if [ "$_DEPLOY_MODE" = "unknown" ] && [ -f ~/.hindsight/config ]; then
_HS_CONFIGURED="yes"
if grep -q "api.hindsight.vectorize.io" ~/.hindsight/config 2>/dev/null; then
_DEPLOY_MODE="cloud"
else
_DEPLOY_MODE="self-hosted"
fi
fi
# 3. Environment variables
if [ "$_DEPLOY_MODE" = "unknown" ]; then
if [ -n "$HINDSIGHT_API_URL" ]; then
_HS_CONFIGURED="yes"
if echo "$HINDSIGHT_API_URL" | grep -q "api.hindsight.vectorize.io"; then
_DEPLOY_MODE="cloud"
else
_DEPLOY_MODE="self-hosted"
fi
elif [ -n "$HINDSIGHT_API_DATABASE_URL" ]; then
_HS_CONFIGURED="yes"
_DEPLOY_MODE="self-hosted"
fi
fi
# 4. Installed tools (least specific — just means tool exists on machine)
if [ "$_HS_CONFIGURED" = "no" ]; then
if command -v hindsight-embed >/dev/null 2>&1; then
_HS_CONFIGURED="yes"
[ "$_DEPLOY_MODE" = "unknown" ] && _DEPLOY_MODE="local"
fi
fi
# Detect existing Hindsight usage in current project
_HAS_EXISTING="no"
if grep -rl "hindsight" --include="*.py" --include="*.ts" --include="*.js" --include="*.json" . 2>/dev/null | head -1 | grep -q .; then
_HAS_EXISTING="yes"
fi
# Detect project language / framework for SDK selection
_LANGUAGE="unknown"
_FRAMEWORK="unknown"
_HAS_NODE="no"
_HAS_PYTHON="no"
if [ -f package.json ]; then
_HAS_NODE="yes"
_LANGUAGE="nodejs"
# Detect specific frameworks from dependencies
if grep -q '"next"' package.json 2>/dev/null; then
_FRAMEWORK="next.js"
elif grep -q '"react"' package.json 2>/dev/null; then
_FRAMEWORK="react"
elif grep -q '"express"' package.json 2>/dev/null; then
_FRAMEWORK="express"
elif grep -q '"fastify"' package.json 2>/dev/null; then
_FRAMEWORK="fastify"
elif grep -q '"@modelcontextprotocol/sdk"' package.json 2>/dev/null; then
_FRAMEWORK="mcp"
fi
fi
if [ -f pyproject.toml ] || [ -f requirements.txt ] || [ -f setup.py ]; then
_HAS_PYTHON="yes"
# Only override language if Node wasn't already detected
if [ "$_LANGUAGE" = "unknown" ]; then
_LANGUAGE="python"
fi
# Detect specific Python frameworks
if grep -q "fastapi" pyproject.toml requirements*.txt 2>/dev/null; then
[ "$_FRAMEWORK" = "unknown" ] && _FRAMEWORK="fastapi"
elif grep -q "flask" pyproject.toml requirements*.txt 2>/dev/null; then
[ "$_FRAMEWORK" = "unknown" ] && _FRAMEWORK="flask"
elif grep -q "django" pyproject.toml requirements*.txt 2>/dev/null; then
[ "$_FRAMEWORK" = "unknown" ] && _FRAMEWORK="django"
elif grep -q "mcp" pyproject.toml requirements*.txt 2>/dev/null; then
[ "$_FRAMEWORK" = "unknown" ] && _FRAMEWORK="mcp"
fi
fi
# Mixed-language project → python takes precedence only if it looks like the primary (has main module)
if [ "$_HAS_NODE" = "yes" ] && [ "$_HAS_PYTHON" = "yes" ]; then
_LANGUAGE="mixed"
fi
# Infer recommended integration method
_INTEGRATION="unknown"
case "$_LANGUAGE" in
nodejs) _INTEGRATION="nodejs-sdk" ;;
python) _INTEGRATION="python-sdk" ;;
mixed) _INTEGRATION="ask" ;;
esac
# If framework is MCP, override
if [ "$_FRAMEWORK" = "mcp" ]; then
_INTEGRATION="mcp"
fi
echo "HINDSIGHT_SKILL_VERSION: $_HS_VERSION"
echo "BRANCH: $_BRANCH"
echo "PROJECT: $_PROJECT"
echo "HINDSIGHT_CONFIGURED: $_HS_CONFIGURED"
echo "DEPLOY_MODE: $_DEPLOY_MODE"
echo "HAS_EXISTING_SETUP: $_HAS_EXISTING"
echo "LANGUAGE: $_LANGUAGE"
echo "FRAMEWORK: $_FRAMEWORK"
echo "INTEGRATION: $_INTEGRATION"
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 · 859 lines · 35 tokens per session scan A 02863c500c9e
hindsight-architect is a skill published in the GitHub repository vectorize-io/hindsight (51,231 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 9,188 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.