A release checklist command for preparing and creating a new SageOx version. It checks the branch, working directory, code quality, integration tests, and smoke tests before release.

Use it to propose or specify a version number, run required checks, and stop the release when a check fails.

It reduces the risk of publishing a version with untested code or a repository in the wrong state.

release — Command by sageox

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 commands/sageox/ox/release

Clone the repo

git clone --depth 1 https://github.com/sageox/ox

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,811 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.01811
Opus 5	$0.00000	$0.00905
Sonnet 5	$0.00000	$0.00362
Haiku 4.5	$0.00000	$0.00181

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

Security

Grade A, and why

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/commands/release.md · 197 lines

How it starts

The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Prepare and create a new ox release.

Use when:

Ready to release a new version of ox
User says "release", "cut a release", "prepare release", "version bump"

Arguments: $ARGUMENTS (optional version number like "0.15.0", or empty to auto-propose)

Release Workflow

Follow these steps exactly:

Step 1: Pre-flight Checks

# Verify on main branch, clean working directory
git branch --show-current
git status

# Run quality gates (run lint and tests in parallel)
make lint
make test-all          # all unit tests incl. expensive (git clone, SQLite, LFS)
make test-slow         # build tag: slow (real ox binary tests)
make test-digital-twin # ledger + team-context structural verification

If tests or lint fail, fix issues before proceeding.

Step 1b: E2E Integration Tests (MANDATORY — requires claude CLI + ANTHROPIC_API_KEY)

make test-integration

This is a hard release gate. These tests launch real Claude Code instances, exercise real hooks, send real SIGINT signals, and verify the full session recording and anti-entropy pipelines end-to-end. Do NOT proceed if integration tests fail.

Step 1c: Smoke Tests (requires SAGEOX_CI_PASSWORD)

make smoke-test

This runs end-to-end tests against test.sageox.ai: auth, init, doctor, status, re-init, agent prime, session list, and clone-without-ox. If smoke tests fail, investigate before proceeding — these verify ox works in a real environment.

Step 1d: Run Walks (Human-Driven)

Coordinate in the Slack channel. A team member installs the release candidate and walks through core workflows on a real machine:

Fresh setup — ox login → ox init on a new repo → ox doctor → ox status
Agent prime — open Claude Code, verify ox agent prime loads team context
Session recording — start a session, do some work, stop it, verify ox session list
Team context — verify team knowledge appears via ox agent team-ctx
Clone experience — clone the repo in a fresh directory, run ox init
Doctor recovery — delete .sageox/config.json, run ox doctor, verify auto-repair
Upgrade path — if upgrading, verify ox version and existing config survive

Read the full file on GitHub · 197 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.

2d ago First seen · 197 lines · 0 tokens per session scan A 2491bf1f2403

Subscribe to this mod's changes

release is a command published in the GitHub repository sageox/ox (50 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,811 tokens. 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.

Code review Memory and context Testing agentic-engineering claude-code codex-cli droid gemini-cli hivemind

om-vault-upgrade

Import and migrate content from an existing Obsidian vault into this obsidian-mind instance. Works with older obsidian-mind versions and arbitrary Obsidian vaults.

breferrari/obsidian-mind · 0 tokens

om-self-review

Write your self-assessment for your company's review tool. Produces project impact descriptions, competency self-assessments (current level / next level), principles, and growth plan — all within character limits, fact-checked, strategically calibrated.

breferrari/obsidian-mind · 0 tokens

release