nemo-relay-plugin

nemo-relay-plugin is a plugin for Claude Code from NVIDIA/NeMo-Relay. Its token cost is not measured, scanned A, original, Apache-2.0.

A NeMo Relay plugin package for the native Relay gateway lifecycle and Claude Code hooks. Hooks are actions that run at defined points in an agent workflow, while observability means seeing what the system is doing locally.

In plain words
What is it for?
Use it when working with NeMo Relay, Claude Code hooks and local visibility into gateway activity.
Why use it?
It connects these lifecycle events and hooks through the plugin’s MCP server configuration.

Plugin for Claude Code ✓ vendor

Written for Claude Code: a Claude Code plugin manifest. Also seen: mentions Claude Code.

Good fit Use it when working with NeMo Relay, Claude Code hooks and local visibility into gateway activity.

Compare 6 plugins from other repositories ↓
Install in Claude Code
/plugin marketplace add NVIDIA/NeMo-Relay
/plugin install nemo-relay-plugin
About the project

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.

NVIDIA/NeMo-Relay · 196 stars · on GitHub · docs.nvidia.com

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.

Clone the repo
git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay

Made for: Claude Code.

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.

agentmods badge for nemo-relay-plugin

README.md
[![agentmods](https://agentmods.dev/badge/plugins/nvidia/nemo-relay/claude-code/github.svg)](https://agentmods.dev/plugins/nvidia/nemo-relay/claude-code)
Your own site
<a href="https://agentmods.dev/plugins/nvidia/nemo-relay/claude-code"><img src="https://agentmods.dev/badge/plugins/nvidia/nemo-relay/claude-code/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.

agentmods 80×15 button for nemo-relay-plugin

Your own site · 80×15
<a href="https://agentmods.dev/plugins/nvidia/nemo-relay/claude-code"><img src="https://agentmods.dev/badge/plugins/nvidia/nemo-relay/claude-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

nemo-relay-plugin 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 7d 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.

integrations/coding-agents/claude-code/.claude-plugin/plugin.json · 20 lines

What it actually says

{
  "name": "nemo-relay-plugin",
  "version": "0.11.0",
  "description": "Native Relay gateway lifecycle and Claude Code hooks for complete local observability.",
  "author": {
    "name": "NVIDIA Corporation and Affiliates",
    "url": "https://github.com/NVIDIA/NeMo-Relay"
  },
  "homepage": "https://github.com/NVIDIA/NeMo-Relay",
  "repository": "https://github.com/NVIDIA/NeMo-Relay",
  "license": "Apache-2.0",
  "mcpServers": "./.mcp.json",
  "keywords": [
    "nemo-relay",
    "claude-code",
    "hooks",
    "observability"
  ]
}
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.

  1. 7d ago Changed 03688c0bae82
  2. 29d ago Changed feb09453c334
  3. 1mo ago First seen · 20 lines scan A 105b717ed4f0

Subscribe to this mod's changes

nemo-relay-plugin is a plugin published in the GitHub repository NVIDIA/NeMo-Relay (196 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.