What is update-project-version?

A release-version update workflow for the NeMo Relay project across Rust, Node.js and lockfiles. Lockfiles record the exact package versions used by a project.

Use it when changing a release, pre-release or build-metadata version in Cargo.toml, npm package files and package-lock.json.

It helps keep the project’s different release surfaces aligned so package metadata and dependency records do not disagree.

update-project-version — Skill for Claude Code and Codex by NVIDIA: A release-version update workflow for the NeMo Relay project…

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/update-project-version

Any agent

npx skills add NVIDIA/NeMo-Relay --skill update-project-version

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nvidia/nemo-relay/update-project-version.svg)](https://agentmods.dev/skills/nvidia/nemo-relay/update-project-version)

Your own site

<a href="https://agentmods.dev/skills/nvidia/nemo-relay/update-project-version"><img src="https://agentmods.dev/badge/skills/nvidia/nemo-relay/update-project-version.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 1,199 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.00026	$0.01199
Opus 5	$0.00013	$0.00600
Sonnet 5	$0.00005	$0.00240
Haiku 4.5	$0.00003	$0.00120

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

Security

Grade A, and why

update-project-version 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 3d 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/update-project-version/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.

Update Project Version

Companion Guidance

Use karpathy-guidelines alongside this skill for implementation or review work. Keep changes scoped, surface assumptions, and define focused validation before editing.

Use this skill when changing the released NeMo Relay version, including pre-release or build-metadata variants used during packaging.

Source Of Truth

Cargo.toml [workspace.package].version is the source of truth for the Rust workspace and Python build versioning.
Keep Cargo.toml [workspace.dependencies] self-references aligned when the workspace version changes.
crates/node/package.json carries its own npm package version and must stay aligned with the workspace-root package-lock.json.
integrations/openclaw/package.json carries the OpenClaw npm plugin version and must stay aligned with the workspace-root package-lock.json.
package-lock.json records Node package versions under packages["crates/node"].version and packages["integrations/openclaw"].version. The workspace-root lockfile may not have a top-level version field.

Workflow

Read the current version from Cargo.toml and decide the exact target version string.
Run just set-version <version> to update release-version source files:
- [workspace.package].version
- workspace.dependencies.nemo-relay.version
- workspace.dependencies.nemo-relay-adaptive.version
- workspace.dependencies.nemo-relay-pii-redaction.version
- workspace.dependencies.nemo-relay-ffi.version
- workspace.dependencies.nemo-relay-cli.version
- crates/node/package.json version
- integrations/openclaw/package.json version
- package-lock.json packages["crates/node"].version
- package-lock.json packages["integrations/openclaw"].version
- integrations/openclaw/package.json dependencies["nemo-relay-node"]
- package-lock.json packages["integrations/openclaw"].dependencies["nemo-relay-node"]
If editing helper code, keep helper inputs aligned with those same fields:
- set_project_version should call the Cargo, Node, and coding-agent plugin version helpers for the same target version.
- set_cargo_workspace_version should update [workspace.package].version plus workspace.dependencies.nemo-relay.version, workspace.dependencies.nemo-relay-adaptive.version, workspace.dependencies.nemo-relay-pii-redaction.version, workspace.dependencies.nemo-relay-ffi.version, and workspace.dependencies.nemo-relay-cli.version.
- set_node_package_versions should update crates/node/package.json, integrations/openclaw/package.json, the corresponding package-lock.json package entries, and the OpenClaw nemo-relay-node dependency entries in both files. set_node_package_version remains a compatibility alias. set_npm_package_version remains the reusable npm JSON helper for Node packaging recipes.
Refresh generated surfaces:
- Run cargo check --workspace to refresh Cargo.lock if workspace package entries changed.
- If Cargo metadata changed and committed attribution files must stay fresh, regenerate ATTRIBUTIONS-Rust.md with ./scripts/generate_attributions.sh rust.
- If package-lock.json changed, regenerate ATTRIBUTIONS-Node.md with ./scripts/generate_attributions.sh node.
Audit remaining references to the old version with targeted search. Separate true version pins from examples, generated attribution files, and unrelated third-party versions.

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.

3d ago First seen · 117 lines · 26 tokens per session scan A fce57902b672

Subscribe to this mod's changes

update-project-version is a skill published in the GitHub repository NVIDIA/NeMo-Relay (132 stars, last pushed 4d ago), licensed Apache-2.0. It adds 26 tokens to every session and 1,199 once invoked, about $0.0001 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.

Git and workflow Releases agents ai atif atof claude-code codex

final-release-review

Perform pre-release planning or a final release-candidate review for openai-agents-python by comparing the target with the previous remote tag, determining the minimum compatible release type, auditing regressions and contract changes, reviewing open documentation PR coverage, drafting minor-release Key Changes, and…

openai/openai-agents-python · 64 tokens

release-candidate-prep

Preflight and prepare an OpenAI Agents Python release candidate in a dedicated worktree from exact origin/main, gate readiness before branch creation, freeze the released API contract, create or replace the local release branch with one release commit, enforce final release review as a checker, and produce…

openai/openai-agents-python · 87 tokens

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

hs-release

Cut a core Hindsight release (vX.Y.Z) and open the changelog + blog PR. Use when asked to cut/start a release, bump the version, or publish a new Hindsight version.

vectorize-io/hindsight · 45 tokens

cli-release

Release and recover first-party Composio CLI binaries through Build CLI Binaries, including automatic beta builds, promote-stable dispatches, beta-tag selection, asset and installation verification, and failed release recovery. Use when a contributor asks to build a CLI beta, publish or promote a stable CLI version…

ComposioHQ/composio · 95 tokens

hunk-release

Prepares, publishes, verifies, and curates Hunk releases. Use for release metadata, benchmarks, tags, publishing, release videos, backports, or recovery.

modem-dev/hunk · 38 tokens