What is prepare-code-freeze?

A procedure for preparing a NeMo Relay code freeze, the point when a release branch is created and changes for that release are stabilized. It also updates the development version and opens the required pull request.

Use it when starting a NeMo Relay release code freeze. It covers creating the release branch, updating nightly alpha configuration, bumping the main branch version, and preparing a pull request.

It organizes the coordinated branch, version, nightly-build, and review changes needed before a release. This reduces manual steps and keeps the release branches connected to the expected upstream repository.

prepare-code-freeze — Skill by NVIDIA

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/nvidia/nemo-relay/prepare-code-freeze

Any agent

npx skills add NVIDIA/NeMo-Relay --skill prepare-code-freeze

Clone the repo

git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay

Made for: Claude Code, Codex.

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 819 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.00037	$0.00819
Opus 5	$0.00018	$0.00409
Sonnet 5	$0.00007	$0.00164
Haiku 4.5	$0.00004	$0.00082

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

Security

Grade A, and why

prepare-code-freeze 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/prepare-code-freeze/SKILL.md · 87 lines

How it starts

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

Prepare Code Freeze

Use this skill when the user asks to start, prepare, or automate a NeMo Relay code freeze.

Companion Guidance

Use update-project-version for version bump semantics and prepare-pr before opening the PR.

Workflow

This workflow assumes upstream is the NVIDIA repository remote (NVIDIA/NeMo-Relay). The origin remote can be a maintainer's personal fork.

Confirm or infer the target release version from upstream/main:Cargo.toml. Derive the release branch as release/<major>.<minor>.
Prompt for <next-version> if the user did not provide it. This is the version that main moves to after the release branch is cut.
Fetch the latest main and create the release branch from upstream/main:
```
git fetch upstream main
git branch release/<major>.<minor> upstream/main
git push upstream release/<major>.<minor>
```
If the remote release branch already exists, verify it points where expected before continuing.
Create a PR branch from latest upstream/main, for example docs/code-freeze-<major>.<minor>.
Update .github/nightly-alpha-branches.yaml to include the new release branch.
Run just set-version <next-version> to bump all release-versioned package surfaces on main. Regenerate the dynamic worker-plugin fixture lockfile so its path dependencies use the new workspace version:
```
cargo generate-lockfile --manifest-path crates/core/tests/fixtures/worker_plugin/Cargo.toml
```
Search documentation source for references to the old version and update current-version install commands, package examples, and configuration examples to <next-version> where appropriate:
```
rg -n '<old-version>' README.md docs fern --glob '!docs/_build/**' || true
```
Review matches before changing them. Leave intentional historical references alone, such as release notes, changelogs, generated build output, and third-party dependency attribution entries.
Validate with targeted checks:

Read the full file on GitHub · 87 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 · 87 lines · 37 tokens per session scan A f92271a94ac5

Subscribe to this mod's changes

prepare-code-freeze is a skill published in the GitHub repository NVIDIA/NeMo-Relay (132 stars, last pushed 3d ago), licensed Apache-2.0. It adds 37 tokens to every session and 819 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.

Code review Git and workflow agents ai atif atof claude-code codex

agent-code-analyzer

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

ruvnet/ruflo · 19 tokens

foundry-config-setup

Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.

microsoft/agent-framework · 65 tokens

haiku

When writing a haiku for this bot, follow these conventions.

agno-agi/agno · 0 tokens

deploy-docker-compose

Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…

omnigent-ai/omnigent · 84 tokens

azure-mgmt-botservice-dotnet

Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".

microsoft/skills · 78 tokens

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

callstack/agent-device · 55 tokens