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/maintain-packaging/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/maintain-packaging)<a href="https://agentmods.dev/skills/nvidia/nemo-relay/maintain-packaging"><img src="https://agentmods.dev/badge/skills/nvidia/nemo-relay/maintain-packaging/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/maintain-packaging"><img src="https://agentmods.dev/badge/skills/nvidia/nemo-relay/maintain-packaging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.00601 |
| Opus 5.5 | $0.00023 | $0.00240 |
| Sonnet 5.5 | $0.00012 | $0.00120 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
maintain-packaging 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintain Release And Packaging Surfaces
Use this skill when a change affects how NeMo Relay is built, packaged, named, or consumed outside the source tree.
Audit Areas
- Rust
Cargo.tomlpackage names and workspace metadata - Python packaging in
pyproject.toml - Python worker plugin SDK packaging in
python/plugin/pyproject.toml - Go module path in
go/nemo_relay/go.mod - Node workspace metadata in root
package.jsonandpackage-lock.json - Node package metadata in
crates/node/package.json - FFI header and library naming
- CI workflows, install commands, and example commands
justfilebuild, test, clean, version, and package recipes for plugin crates and packages- Release tags, release-note surfaces, and registry-facing version translation
Checklist
- Every new package or plugin has an explicit versioning model: either it participates in the unified NeMo Relay release or it has an intentionally independent source of truth
- Package names, import paths, and module names are internally consistent
- Generated artifacts still land where downstream consumers expect
- Docs and examples use the current install/import/build commands
- CI references the same package names as local workflows
- Public packaging changes are reflected in release-facing docs
- For a new unified-release surface, its manifest version, lockfile entry,
and internal NeMo Relay version pins are covered by
set_project_versionin thejustfile; extend the owning helper and its fail-fast field checks in the same change when a value is not derived automatically, without adding a separate test that mirrors the helper's field list -
nemo-relay-pluginRust and Python packages track the project SemVer policy and Python wheels use valid PEP 440 translation - Release tags still use raw SemVer without a leading
v - Release history and release notes still point to GitHub Releases, not
CHANGELOG.mdor docs pages
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.
- 1mo ago Changed · +1 lines · +35 tokens per session 461cb3e692f2
- 1mo ago First seen · 59 lines · 23 tokens per session scan A c5087240edbe
maintain-packaging is a skill published in the GitHub repository NVIDIA/NeMo-Relay (212 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 601 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.
Other skills, from other repositories
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.
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
create-tech-design
Only use when the user explicitly invokes this skill by name.
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…
haiku
When writing a haiku for this bot, follow these conventions.
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.