OpenShell: Skill for Claude Code

.agents/skills/release-captain/SKILL.md

release-captain is a skill for Claude Code, Codex from NVIDIA/OpenShell. It costs 86 tokens per session (2,861 once invoked), scanned A, original, Apache-2.0.

A checklist and workflow for serving as the OpenShell release captain. It covers preparing a pre-release, checking failures, publishing the approved stable release, and starting the next release cycle.

In plain words
What is it for?
Use it to check release workflows, coordinate final merges, cut an approved release, verify publication, and recover from failed pre-releases.
Why use it?
It turns a recurring release process into explicit weekday steps and requires approval before actions such as pushing tags or merging changes.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is NVIDIA/OpenShell's own configuration. It tells Claude Code and Codex how to work on OpenShell itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything OpenShell configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is (cd "$wt" && GITHUB_REPOSITORY=NVIDIA/OpenShell uv run -q --no-project python tasks/scripts/select-release-candidate.py "$VERSION" --branch main | jq .).

About the project

OpenShell is a runtime for autonomous AI agents that executes them in sandboxed environments governed by declarative policies. It is used to restrict agents' access to files, credentials, data, and network resources, and the catalogue includes skills and workflows for operating and contributing to it.

NVIDIA/OpenShell · 21,172 stars · on GitHub · docs.nvidia.com

Reuse

Borrowing it

Nothing to install: this file belongs to NVIDIA/OpenShell. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/NVIDIA/OpenShell/main/.agents/skills/release-captain/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/NVIDIA/OpenShell

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for release-captain

README.md
[![agentmods](https://agentmods.dev/badge/skills/nvidia/openshell/release-captain/github.svg)](https://agentmods.dev/skills/nvidia/openshell/release-captain)
Your own site
<a href="https://agentmods.dev/skills/nvidia/openshell/release-captain"><img src="https://agentmods.dev/badge/skills/nvidia/openshell/release-captain/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.

agentmods 80×15 button for release-captain

Your own site · 80×15
<a href="https://agentmods.dev/skills/nvidia/openshell/release-captain"><img src="https://agentmods.dev/badge/skills/nvidia/openshell/release-captain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,861 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00086 $0.02861
Opus 5.5 $0.00034 $0.01144
Sonnet 5.5 $0.00017 $0.00572
Haiku 4.5 $0.00009 $0.00286

Measured 2d ago against content hash 407ce905d826, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-captain 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.

.agents/skills/release-captain/SKILL.md · 234 lines

How it starts

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

Release Captain

OpenShell publishes a stable release every Tuesday from a qualified pre-release (RFC 0014). The release captain keeps the week's pre-release train green, coordinates the last merges, cuts the release, and starts the next train.

How to use this skill

When Ask What happens
The week before your turn "I'm release captain next week. Is the train ready?" Checks that the next version's -pre.1 exists. If not, ask this week's captain to start the train (Tuesday step 6). Then check each weekday that Auto-Tag's pre-release ran and passed (gh run list --workflow release-prerelease.yml --limit 3), and fix failures as they happen (Monday step 3) instead of on Monday.
Monday "Run the release captain Monday checklist." Monday steps 1–4.
A pre-release failed "vX.Y.Z-pre.N failed, help me fix it." Monday step 3 and Recovery.
Tuesday "Cut the release." Tuesday steps 1–6, ending with starting the next train.

Guardrails

Get explicit approval, with the exact command and target SHA, before pushing a tag, dispatching, rerunning, or cancelling a workflow, merging or approving a PR, or posting in Slack or GitHub. Never repoint a stable tag, delete a -pre.N tag, or start a second Pre-release run for a tag; it has no concurrency guard.

How the train works

  • A train has one base version, such as v0.1.4, fixed by its -pre.1 tag. A patch train can't take breaking changes to Stable interfaces.
  • Release Auto-Tag runs on weekdays at 14:00 Europe/Zurich. If main has commits since the latest -pre.N, it tags the next one and dispatches Pre-release (release-prerelease.yml, about 45 minutes). It skips when the train has no -pre.1 or the base version is already stable.
  • Pre-release builds, then publishes and qualifies in parallel, and writes a release-notes preview artifact. Pushing a -pre.N tag by hand starts it.
  • Release (release.yml) is dispatched by hand with the stable version. It picks the highest -pre.N on main whose whole Pre-release run passed, creates the stable tag on that commit, and publishes without requalifying.
  • Stable releases publish public schemas to buf.build/openshell/core with the release tag as the label; prereleases skip Buf publication. The Buf repository must exist and Actions must have a BUF_TOKEN secret with write access. A failed Buf push fails the release run; follow Recovery before rerunning the failed publication job.

Read the full file on GitHub · 234 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 Changed · +5 lines 407ce905d826
  2. 3d ago Changed · -15 lines 6ef2e88a6230
  3. 9d ago Changed · +15 lines 67b89b531113
  4. 16d ago First seen · 229 lines · 86 tokens per session scan A d9674b917c27

Subscribe to this mod's changes

release-captain is a skill published in the GitHub repository NVIDIA/OpenShell (21,172 stars, last pushed yesterday), licensed Apache-2.0. It adds 86 tokens to every session and 2,861 once invoked, about $0.0003 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-10-22.

Related

release-captain compared with skills from other repositories

release-captain next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
release-captainNVIDIA/OpenShellSkill21kyesterdayApache-2.0A86Claude Code, Codex
release-announcementpaperclipai/paperclipSkill111ktodayMITA42Claude Code, Codex
releasethedotmack/claude-memSkill114ktodayApache-2.0A13Claude Code
release-notesphuryn/pm-skillsSkill28k8d agoMITA57Claude Code
multi-agent-release-managerchromium/chromiumSkill25ktodayBSD-3-ClauseA27Claude Code, Codex
pack-submitaeonfun/aeonSkill788yesterdayMITA27Claude Code, Codex
updater_guidesiddsachar/row-botSkill1.7ktodayApache-2.0A22Claude Code, Codex