hs-release

A release procedure for publishing a new version of Hindsight, a system that gives AI agents long-term memory.

In plain words
What is it for?
Starting a core Hindsight release, updating its version, tagging the code, and opening the related changelog and blog pull request.
Why use it?
It guides the version change, changelog and blog updates, while checking that the right fixes are on the main code branch before publishing.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/vectorize-io/hindsight/hs-release
Any agent
npx skills add vectorize-io/hindsight --skill hs-release
Clone the repo
git clone --depth 1 https://github.com/vectorize-io/hindsight

Made for: Claude Code, Codex.

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,435 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00045 $0.01435
Opus 5 $0.00023 $0.00718
Sonnet 5 $0.00009 $0.00287
Haiku 4.5 $0.00005 $0.00144

Measured 2d ago against content hash 41caeacb671b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

.claude/skills/hs-release/SKILL.md · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 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

  1. Decide the base. A release is cut from the latest origin/main, never from a feature branch. git fetch origin --tags first. Confirm the "couple of fixes" the user means are actually merged to main (git log v<prev>..origin/main --oneline).
  2. Find where main is checked out. main is often already checked out in a sibling worktree (git worktree list). You cannot check out main in 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 to origin/main, run the release, then git stash pop.
  3. Pitfall: never pipe the checkout in an && chain like git checkout main 2>&1 | tail && git reset --hard ... — the pipe's exit status is tail's (always 0), so a failed checkout won't stop the chain and the reset fires on the wrong branch. Check out as its own command and verify git branch --show-current before 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.

Read the full file on GitHub · 117 lines

Changes

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.

  1. 2d ago First seen · 117 lines · 45 tokens per session scan A 41caeacb671b

Subscribe to this mod's changes

hs-release is a skill published in the GitHub repository vectorize-io/hindsight (21,822 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 1,435 once invoked, about $0.0002 per session on Opus 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.

Related

Other skills, from other repositories

nocturnusai-knowledge

Use when working with NocturnusAI facts and rules — asserting (tell), querying (ask/infer), teaching rules (teach), retracting (forget), bulk operations, aggregation, or discovering predicates. Covers the core knowledge base CRUD operations. Triggers on: tell, ask, teach, forget, assert, query, infer, rule, fact…

Auctalis/nocturnusai · 92 tokens

nocturnusai-memory

Use when working with NocturnusAI agent memory — context windows, salience scoring, temporal queries, recall, consolidation, decay, TTL, expiration, event streaming, or memory lifecycle management. Triggers on: memory, context window, salience, temporal, recall, consolidate, decay, TTL, expire, events, NocturnusAI…

Auctalis/nocturnusai · 81 tokens

nocturnusai-admin

Use when managing NocturnusAI databases, tenants, health checks, metrics, backups, API key management, RBAC configuration, admin operations, or operational monitoring. Triggers on: NocturnusAI database, tenant, health, metrics, backup, API key, RBAC, admin, monitoring, operational.

Auctalis/nocturnusai · 72 tokens

nocturnusai-connect

Use when setting up NocturnusAI connection, configuring MCP server in claudedesktopconfig.json or .mcp.json, setting up API keys, auth, RBAC bootstrap, creating databases/tenants, or troubleshooting connection issues. Triggers on: setup, connect, configure, MCP, auth, API key, tenant, database, bootstrap, NocturnusAI.

Auctalis/nocturnusai · 85 tokens

nocturnusai-reasoning

Use when working with NocturnusAI advanced reasoning — negation-as-failure (NAF), scopes (fork/merge/diff), hypothetical reasoning, confidence scores, conflict resolution strategies, or proof chains. Triggers on: NAF, negation, negation-as-failure, scope, fork, merge, hypothesis, confidence, conflict, proof, what-if…

Auctalis/nocturnusai · 92 tokens

agent-pagerank-analyzer

Agent skill for pagerank-analyzer - invoke with $agent-pagerank-analyzer.

ruvnet/ruflo · 24 tokens