NeMo-Relay AGENTS.md

A project instruction file for NeMo Relay, a runtime framework for running AI-agent work across Rust, Python, and Node.js. It describes scopes, middleware, plugins, events, and monitoring integrations.

In plain words
What is it for?
Use it when developing or navigating NeMo Relay, especially its core runtime, bindings, plugins, lifecycle events, and telemetry exporters.
Why use it?
It gives coding agents a map of the framework and its repository before they change code. This makes it clearer where runtime behavior, language bindings, integrations, and observability belong.

Instructions file for CodexOpenCode

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.

agentmods
npx agentmods add instructions/nvidia/nemo-relay/agents-md
Clone the repo
git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay

Made for: Codex, OpenCode.

Per session 2,587 This file is loaded in full into every session.
When invoked 2,587 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.02587 $0.02587
Opus 5 $0.01293 $0.01293
Sonnet 5 $0.00517 $0.00517
Haiku 4.5 $0.00259 $0.00259

Measured 2d ago against content hash aee4f1195b6b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

NeMo-Relay AGENTS.md 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 2d 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.

AGENTS.md · 223 lines

How it starts

The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

This file provides guidance to agents, including Claude Code and OpenAI Codex, when working in this repository.

Project Overview

NeMo Relay is a multi-language agent runtime framework for execution scopes, lifecycle events, middleware, plugins, and observability around tool and LLM calls. The core runtime is Rust. Primary supported bindings are Rust, Python, and Node.js. Go and the raw C FFI are experimental and source-first.

The shared runtime model is:

  1. Scope stacks decide where work belongs and which scope-local behavior is visible.
  2. Middleware registries decide what guardrails and intercepts run around managed calls.
  3. Plugins install reusable runtime behavior from configuration.
  4. Events record runtime behavior in ATOF form.
  5. Subscribers and exporters consume events in-process or export them to ATIF, OpenTelemetry, OpenInference, or other backends.

Repository Structure

The repository layout separates the Rust runtime, language bindings, documentation, integrations, and agent-facing skills.

crates/
  core/       # Rust core runtime crate, published as nemo-relay
  adaptive/   # Adaptive runtime primitives and plugin components
  python/     # PyO3 native extension for the Python package
  ffi/        # Raw C ABI layer used by downstream bindings such as Go
  node/       # NAPI Node.js binding and JavaScript/TypeScript entry points
python/
  nemo_relay/  # Python wrapper package: scopes, tools, LLM, middleware, typed helpers, plugins, adaptive helpers
  tests/      # Python tests
go/
  nemo_relay/  # Experimental Go CGo binding and tests
fern/         # Fern documentation site
scripts/      # Stable wrappers and helper scripts; build/test/docs entry points live in justfile
skills/       # Published Codex/agent skills for NeMo Relay usage patterns

Prerequisites

Install the tools needed for the surfaces you touch. For a full repository validation environment, install all of these:

Tool Version / Notes Required For
Rust Docs minimum is 1.86 or newer; the repo pins the active toolchain in rust-toolchain.toml Rust core, native bindings, FFI
Python 3.11 or newer Python package, PyO3 builds, docs tooling
Node.js 24 or newer, with npm Node.js binding, generated API docs
Go 1.21 or newer Experimental Go binding
uv Current project workflow tool Python environments, docs dependencies, pre-commit
just 1.40 or newer Canonical build, test, docs, package task runner
cargo-deny Current stable Rust dependency auditing
cargo-about 0.9.1 Rust dependency attribution generation
cargo-nextest 0.9.111 or newer CI-style Rust test runs
cargo-llvm-cov 0.8.5 or newer CI-style coverage reports

Read the full file on GitHub · 223 lines

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. 2d ago First seen · 223 lines · 2,587 tokens per session scan A aee4f1195b6b

Subscribe to this mod's changes

NeMo-Relay AGENTS.md is an instructions file published in the GitHub repository NVIDIA/NeMo-Relay (132 stars, last pushed 2d ago), licensed Apache-2.0. It adds 2,587 tokens to every session, about $0.0129 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.