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 agentmods add skills/nvidia/nemo-relay/test-go-bindingnpx skills add NVIDIA/NeMo-Relay --skill test-go-bindinggit clone --depth 1 https://github.com/NVIDIA/NeMo-RelayWhat 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 | $0.00028 | $0.00597 |
| Opus 5 | $0.00014 | $0.00298 |
| Sonnet 5 | $0.00006 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
test-go-binding 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 3d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build And Test Go Binding
Companion Guidance
Use karpathy-guidelines alongside this skill for implementation or review
work. Keep changes scoped, surface assumptions, and define focused validation
before editing.
Use this skill when the change is primarily in go/nemo_relay or the Go
binding behavior it depends on.
Important Constraint
The Go binding links against the shared FFI library. just test-go
builds that library for you, while just build-go remains useful when
you want an explicit build-only pass or need the artifact for other work.
Default Path
- Format changed Go packages with
cd go/nemo_relay && go fmt ./.... - Run Go tests with
just test-go. - If any Rust files changed as part of the Go work, also run
cargo fmt --all,just test-rust, andcargo clippy --workspace --all-targets -- -D warnings. - Use
just build-gowhen you want an explicit build-only pass. - Use
just ci=true test-gowhen you need the CI-style coverage and JUnit path. - Expand to broader validation only if the change touched shared semantics.
Common Commands
# Full Go suite
just test-go
# Format Go files
cd go/nemo_relay && go fmt ./...
# Required when the Go change also touched Rust code
cargo fmt --all
just test-rust
cargo clippy --workspace --all-targets -- -D warnings
# CI-style Go suite with coverage and JUnit artifacts
just ci=true test-go
# Explicit shared-library build when needed separately
just build-go
In the test-go task, the ci variable is what is_true "{{ ci }}" checks.
Setting ci=true enables coverage_out and junit_out handling and adds
-coverprofile=coverage.out to go_test_cmd.
On macOS, also set DYLD_LIBRARY_PATH to the same ../../target/release
directory before running the raw go test command directly.
When To Escalate
- If the change touched
crates/ffi, also usetest-ffi-surface. - If the change touched
crates/coreor shared runtime semantics, also usevalidate-change.
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.
- 3d ago First seen · 78 lines · 28 tokens per session scan A 39ef261ba5e7
test-go-binding is a skill published in the GitHub repository NVIDIA/NeMo-Relay (132 stars, last pushed 3d ago), licensed Apache-2.0. It adds 28 tokens to every session and 597 once invoked, about $0.0001 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
golang-testing-patterns
Modern Go testing patterns including table-driven tests, subtests, test organization, and best practices. Use when writing or refactoring tests, implementing test coverage, or when the user asks about Go testing approaches.
test-go
Write, review, and improve Go test code for this project. Use whenever generating, reviewing, or modifying Go tests - including when invoked by the Tester agent, the /test prompt, or any test-related request. Covers table-driven tests, subtests, t.Parallel(), test helpers with t.Helper(), error assertions via…
go-testing-with-testify
Use when writing, reviewing, or hardening Go tests that rely on stretchr/testify — assert, require, mock, and suite — including table-driven tests, subtests, parallel tests, mocks versus hand-written fakes, error-wrap assertions, and flaky test triage with -race and -count.
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-testing
Go testing best practices.
golang-stretchr-testify
Comprehensive guide to stretchr/testify for Golang testing. Covers assert, require, mock, and suite packages in depth. Use when writing tests with testify, creating mocks, setting up test suites, or choosing between assert and require. Covers testify assertions, mock expectations, argument matchers, call verification…