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.
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.
curl -O https://raw.githubusercontent.com/NVIDIA/NeMo-Relay/main/.agents/skills/check-release-deployments/SKILL.mdgit clone --depth 1 https://github.com/NVIDIA/NeMo-RelayWrote 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.
[](https://agentmods.dev/skills/nvidia/nemo-relay/check-release-deployments)<a href="https://agentmods.dev/skills/nvidia/nemo-relay/check-release-deployments"><img src="https://agentmods.dev/badge/skills/nvidia/nemo-relay/check-release-deployments/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.
<a href="https://agentmods.dev/skills/nvidia/nemo-relay/check-release-deployments"><img src="https://agentmods.dev/badge/skills/nvidia/nemo-relay/check-release-deployments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00050 | $0.00377 |
| Opus 5.5 | $0.00020 | $0.00151 |
| Sonnet 5.5 | $0.00010 | $0.00075 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
check-release-deployments scanned grade A with 1 finding 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 21d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
The checker requires Bash, `curl`, `gh`, `jq`, `just`, and `uv`. Authenticate What it actually says
Check Release Deployments
Require the release tag as input. Do not infer it from the current checkout, Git history, or package metadata.
The checker requires Bash, curl, gh, jq, just, and uv. Authenticate
gh for NVIDIA/NeMo-Relay and verify it with gh auth status. The checker
does not run on Windows. From the repository root, run:
.agents/skills/check-release-deployments/scripts/check_release_deployments.sh <tag>
It validates Relay's raw-SemVer tag format, converts the version to PEP 440 for
PyPI, and checks the published package sets documented in RELEASING.md. It
also verifies that the source-first Go module is present at the tag and reports
the release-related GitHub Actions jobs. Registry checks run only after their
publication jobs are verified successful. If the tag or release jobs cannot be
verified, package checks are skipped.
☑means the exact package version is deployed.○means that exact package version is not deployed.000means a lookup or response could not be verified.- Other numeric values are HTTP statuses returned by the registry.
The Go row checks the tagged go.mod source because Relay does not publish a
separate Go package-manager artifact.
This is a read-only workflow. Do not retry an absent or failed deployment by publishing packages unless the user separately asks to publish.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 21d ago First seen · 37 lines · 50 tokens per session scan A 9dc88b9cd829
check-release-deployments is a skill published in the GitHub repository NVIDIA/NeMo-Relay (196 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 377 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-26.
Other skills, from other repositories
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
ship
Push, open a PR, and watch CI; land mode merges and cleans branches. Triggers "ship it", "create PR", "babysit CI", "land it", "fix CI and merge".
zb-release-pipeline
Generate a GitHub Actions pipeline that builds a zb (Zero Dependencies Builder) project and publishes a GitHub Release with the produced JAR. Use whenever the user wants CI/CD, a build pipeline, a release workflow, or GitHub Actions for a zb-based Java project — phrases like "set up GitHub Actions for this zb…
aiox-devops
Activate Gage (devops) for GitHub Repository Manager & DevOps Specialist. Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized to push to remote repository.
aiox-devops
GitHub Repository Manager & DevOps Specialist (Gage). Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized...
hatch3r-release
Cuts a release with version bump, changelog, tagging, and deploy verification. Use when preparing a release, cutting a version, or deploying to production.