agentmods.dev

NeMo-Relay: Skill for Claude Code

.agents/skills/prepare-code-freeze/SKILL.md

prepare-code-freeze is a skill for Claude Code, Codex from NVIDIA/NeMo-Relay. It costs 47 tokens per session (823 once invoked), scanned A, original, Apache-2.0.

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.

In plain words
What is it for?
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.
Why use it?
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.

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/NeMo-Relay's own configuration. It tells Claude Code and Codex how to work on NeMo-Relay 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 NeMo-Relay configures →

not rated 196repo +4 changed 1mo ago A scan SkillSpector: pass 47 tokens original Apache-2.0
View source ↗ NVIDIA/NeMo-Relay docs.nvidia.com
About the project

NVIDIA/NeMo-Relay is a runtime and library that gives coding agents and applications shared control over agent execution scopes, policies, plugins, lifecycle events, and observability data. It is for developers who need to inspect or instrument runs from agents such as Codex or Claude Code, or integrate frameworks and export traces and trajectories. The catalogue entries provide Relay plugins, hooks, instructions, skills, and an MCP server for those workflows.

NVIDIA/NeMo-Relay · 196 stars · on GitHub · docs.nvidia.com

Reuse

Borrowing it

Nothing to install: this file belongs to NVIDIA/NeMo-Relay. 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/NeMo-Relay/main/.agents/skills/prepare-code-freeze/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay

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 prepare-code-freeze

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/nvidia/nemo-relay/prepare-code-freeze"><img src="https://agentmods.dev/badge/skills/nvidia/nemo-relay/prepare-code-freeze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 823 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00047 $0.00823
Opus 5.5 $0.00019 $0.00329
Sonnet 5.5 $0.00009 $0.00165
Haiku 4.5 $0.00005 $0.00082

Measured 1mo ago against content hash 735e5e7d073c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

.agents/skills/prepare-code-freeze/SKILL.md · 83 lines

How it starts

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

Workflow

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

  1. Confirm or infer the target release version from upstream/main:Cargo.toml. Derive the release branch as release/<major>.<minor>.

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

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

  4. Create a PR branch from latest upstream/main, for example chore/version-bump-<major>.<minor>.

  5. Update .github/nightly-alpha-branches.yaml to include the new release branch.

  6. Run just set-version <next-version> to update all project-owned unified-release version surfaces on main, including Cargo, Python, Node, plugins, lockfiles, and coding-agent manifests. 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

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

  8. Validate with targeted checks:

Read the full file on GitHub · 83 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. 1mo ago Changed 735e5e7d073c
  2. 1mo ago Changed · -4 lines · +10 tokens per session f752aeece529
  3. 1mo 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 (196 stars, last pushed today), licensed Apache-2.0. It adds 47 tokens to every session and 823 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.

Claude CodeGit and workflowReleasesagentsaiatifatofcodex
Related

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…

microsoft/agent-framework · 103 tokens

release-publish

Publish an approved Orchard release.

rohitg00/ai-engineering-from-scratch · 9 tokens

release-review

Review Orchard deployment manifests.

rohitg00/ai-engineering-from-scratch · 7 tokens

orchard-release

Check deployment evidence and recovery conditions.

rohitg00/ai-engineering-from-scratch · 11 tokens

release-notes

Draft short release notes from a list of changes. Use when the user asks for changelogs, release notes, or a concise product update.

cloudflare/agents · 33 tokens

orchard-review

Review a release proposal.

rohitg00/ai-engineering-from-scratch · 8 tokens