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.
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.
npx skills add NVIDIA/NeMo-Relay --skill nemo-relay-integrate-upstreamgit 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/nemo-relay-integrate-upstream)<a href="https://agentmods.dev/skills/nvidia/nemo-relay/nemo-relay-integrate-upstream"><img src="https://agentmods.dev/badge/skills/nvidia/nemo-relay/nemo-relay-integrate-upstream/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/nemo-relay-integrate-upstream"><img src="https://agentmods.dev/badge/skills/nvidia/nemo-relay/nemo-relay-integrate-upstream.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.00080 | $0.02587 |
| Opus 5.5 | $0.00032 | $0.01035 |
| Sonnet 5.5 | $0.00016 | $0.00517 |
| Haiku 4.5 | $0.00008 | $0.00259 |
Grade A, and why
nemo-relay-integrate-upstream 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 2mo 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrate Relay Into An Agent Harness
Use this skill to determine the right NeMo Relay integration for an agent framework or harness that lacks support or needs deeper coverage. First identify how the host runs tools, model calls, streams, subagents, and lifecycle events and what its extension points can control. Then choose the integration depth and Relay attachment methods that meet the required coverage and fit the host's architecture, support model, and lifecycle, using an extension, separate adapter, core wiring, or hybrid as appropriate.
Choose The Work Mode
Choose one mode from the user's request. Do not silently move from assessment to implementation.
- Assess: Determine whether and how Relay can integrate. Inspect only; do not edit the host, Relay, issues, or pull requests. Read Assess The Host.
- Implement: Make an already approved integration change. Reconfirm the exact boundary and read Implement The Integration.
- Qualify: Test an existing integration at an exact host and Relay revision. Treat this as read-only unless the user also requests fixes. Read Qualify The Integration.
If the host already has a maintained Relay integration, treat it as the starting point and verify its coverage against the requested outcome. Use it when it owns the required boundaries. When it does not, identify the missing ownership and evaluate whether to extend the existing integration, combine it with another attachment method, or move a named boundary deeper into host core. Do not create a competing adapter without first proving that gap. Moving from a host plugin to core may be appropriate when requirements need deeper execution ownership or when the intended first-party support, lifecycle, performance, and release model call for core integration. Hermes uses core to own real callbacks and lifecycle rather than relying on its former observability plugin.
What ships with it
9 files 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.
- 2mo ago First seen · 225 lines · 80 tokens per session scan A da5d42626f1b
nemo-relay-integrate-upstream is a skill published in the GitHub repository NVIDIA/NeMo-Relay (234 stars, last pushed yesterday), licensed Apache-2.0. It adds 80 tokens to every session and 2,587 once invoked, about $0.0003 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.
nemo-relay-integrate-upstream compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| nemo-relay-integrate-upstreamNVIDIA/NeMo-Relay | Skill | 234 | yesterday | Apache-2.0 | A | 80 | Claude Code, Codex |
| foundry-config-setupmicrosoft/agent-framework | Skill | 15k | yesterday | MIT | A | 65 | Claude Code, Codex |
| rowboat-spacesrowboatlabs/rowboat | Skill | 18k | yesterday | Apache-2.0 | A | 60 | Claude Code, Codex |
| create-tech-designhumanlayer/humanlayer | Skill | 13k | yesterday | Apache-2.0 | A | 16 | Claude Code, Codex |
| deploy-docker-composeomnigent-ai/omnigent | Skill | 11k | yesterday | Apache-2.0 | A | 84 | Claude Code, Codex |
| haikuagno-agi/agno | Skill | 43k | yesterday | Apache-2.0 | A | 0 | Claude Code, Codex |
| fastapi-router-pymicrosoft/skills | Skill | 3.2k | yesterday | MIT | A | 46 | Claude Code |