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.
Borrowing it
Nothing to install: this file belongs to vectorize-io/hindsight. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vectorize-io/hindsight/main/.claude/skills/hs-release/SKILL.mdgit 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/hs-release)<a href="https://agentmods.dev/skills/vectorize-io/hindsight/hs-release"><img src="https://agentmods.dev/badge/skills/vectorize-io/hindsight/hs-release/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/hs-release"><img src="https://agentmods.dev/badge/skills/vectorize-io/hindsight/hs-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- 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 Tool Misuse · line 28 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 109 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium MCP Rug Pull · line 92 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.00045 | $0.01527 |
| Opus 5.5 | $0.00018 | $0.00611 |
| Sonnet 5.5 | $0.00009 | $0.00305 |
| Haiku 4.5 | $0.00005 | $0.00153 |
Grade A, and why
hs-release 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hindsight Release
Cut a core Hindsight release and open the accompanying changelog/blog PR. This is for the core
product version (API, clients, CLI, control plane, Helm). Integrations are versioned
independently — use scripts/release-integration.sh for those, not this skill.
The release is irreversible and outward-facing: it tags a version and pushes it straight to
main, which triggers CI that publishes packages to PyPI / npm / Helm. Confirm the version number
and that the intended fixes are already merged to main before you start.
Step 0 — Pre-flight
- Decide the base. A release is cut from the latest
origin/main, never from a feature branch.git fetch origin --tagsfirst. Confirm the "couple of fixes" the user means are actually merged tomain(git log v<prev>..origin/main --oneline). - Find where
mainis checked out.mainis often already checked out in a sibling worktree (git worktree list). You cannot check outmainin a second worktree — run the release in the worktree that already holds it. If that worktree is dirty with throwaway cruft (.next-*tsconfig paths, screenshots),git stash push -u, fast-forward toorigin/main, run the release, thengit stash pop. - Pitfall: never pipe the checkout in an
&&chain likegit checkout main 2>&1 | tail && git reset --hard ...— the pipe's exit status istail's (always 0), so a failed checkout won't stop the chain and theresetfires on the wrong branch. Check out as its own command and verifygit branch --show-currentbefore resetting.
Step 1 — Cut the release
Run from the worktree on a clean main:
./scripts/release.sh <version> # e.g. 0.8.1 (no leading v)
release.sh bumps the version in every component, regenerates the OpenAPI spec + all client SDKs,
updates docs versioning, commits Release v<version>, tags v<version>, and pushes the commit
and tag directly to main. The push triggers the Release GitHub Actions workflow that builds
and publishes the packages. It is not a PR.
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 Changed · +5 lines 2911849170e4
- 2mo ago First seen · 117 lines · 45 tokens per session scan A 41caeacb671b
hs-release is a skill published in the GitHub repository vectorize-io/hindsight (55,527 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 1,527 once invoked, about $0.0002 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
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
potpie-graph
Use when the task can read or write the project-memory graph through the potpie CLI: discover the contract with graph catalog, read named views with graph read, resolve entity identity with graph search-entities, create validated plans with graph propose, commit plans with graph commit --verify, inspect quality with…
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent. Use when a pipeline conductor session is seeded, inspected or debugged. You MANAGE one issue/PR pipeline on one repo: two columns per item (session working? item solved?), send intent, never re-derive a red yourself.
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.
release-notes
Create release notes for a new version tag. Gathers all commits, PRs, issues fixed, and breaking changes since a previous release. Creates the release notes markdown file, tags the repo, and pushes. Asks the user to confirm the base version to diff against.