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-migrate-from-flowgit 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-migrate-from-flow)<a href="https://agentmods.dev/skills/nvidia/nemo-relay/nemo-relay-migrate-from-flow"><img src="https://agentmods.dev/badge/skills/nvidia/nemo-relay/nemo-relay-migrate-from-flow/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-migrate-from-flow"><img src="https://agentmods.dev/badge/skills/nvidia/nemo-relay/nemo-relay-migrate-from-flow.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.01764 |
| Opus 5 | $0.00029 | $0.00882 |
| Sonnet 5 | $0.00012 | $0.00353 |
| Haiku 4.5 | $0.00006 | $0.00176 |
Grade A, and why
nemo-relay-migrate-from-flow 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 9d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate From NeMo Flow To NeMo Relay
Use this skill when a user has existing NeMo Flow code or documentation and wants it converted to NeMo Relay. Treat the migration as a mechanical rename plus language-specific validation, not a behavior rewrite. Keep compatibility exceptions explicit before applying broad renames.
Default Workflow
- Inspect the working tree and identify touched surfaces: Rust, Python, Node.js, Go, C FFI, CLI/config, docs, or integrations.
- Resolve
SKILL_DIRto the absolute directory containing thisSKILL.mdandTARGET_PATHto the source repository or target project. Run the bundled helper in dry-run mode before editing:python3 "$SKILL_DIR/scripts/migrate_from_nemo_flow.py" "$TARGET_PATH" --rename-paths - Review the reported text edits, path renames, and legacy project
configuration warnings with the user. Do not migrate project-local
.nemo-flow/config.tomlor.nemo-flow/plugins.tomlinto.nemo-relay. Move those settings manually to a supported user or explicit configuration path after review. - Obtain explicit confirmation for the resolved target root, then rerun with
--write,--rename-paths, and--confirm-root "$TARGET_PATH". - Apply language-specific cleanup for package manager lockfiles, generated artifacts, and public API examples.
- Search for remaining Flow names and verify the affected language surfaces.
Mechanical Rename Map
- Brand and repository:
NeMo Flow->NeMo Relay,NeMo-Flow->NeMo-Relay - Python:
nemo-flow->nemo-relay,nemo_flow->nemo_relay,python/nemo_flow->python/nemo_relay - Rust:
nemo-flow->nemo-relay,nemo-flow-adaptive->nemo-relay-adaptive,nemo_flow::->nemo_relay:: - Node.js:
nemo-flow-node->nemo-relay-node, including related entry points such as/typed,/plugin,/adaptive, and/observability - Go:
github.com/NVIDIA/NeMo-Flow/go/nemo_flow->github.com/NVIDIA/NeMo-Relay/go/nemo_relay, package aliasesnemo_flow->nemo_relay, and source directoriesgo/nemo_flow->go/nemo_relay - C FFI:
nemo_flow.h->nemo_relay.h,nemo_flow_*->nemo_relay_*,NemoFlow*->NemoRelay*, andNEMO_FLOW_*->NEMO_RELAY_* - CLI/config:
nemo-flow->nemo-relay,~/.config/nemo-flow->~/.config/nemo-relay,NEMO_FLOW_*->NEMO_RELAY_*, andx-nemo-flow-*->x-nemo-relay-*. Do not blindly rename project-local.nemo-flow/config.tomlor.nemo-flow/plugins.tomlinto.nemo-relay; those files require manual migration to a supported user or explicit configuration path.
What ships with it
5 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.
- 9d ago First seen · 143 lines · 58 tokens per session scan A 7d7b73f958c6
nemo-relay-migrate-from-flow is a skill published in the GitHub repository NVIDIA/NeMo-Relay (167 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 1,764 once invoked, about $0.0003 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.
Other skills, from other repositories
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
verify-dotnet-samples
How to build, run and verify the .NET sample projects in the Agent Framework repository. Use this when a user wants to verify that the samples still function as expected.