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/prepare-prnpx skills add NVIDIA/NeMo-Relay --skill prepare-prgit 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/prepare-pr)<a href="https://agentmods.dev/skills/nvidia/nemo-relay/prepare-pr"><img src="https://agentmods.dev/badge/skills/nvidia/nemo-relay/prepare-pr.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00039 | $0.00980 |
| Opus 5 | $0.00019 | $0.00490 |
| Sonnet 5 | $0.00008 | $0.00196 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade A, and why
prepare-pr 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 4d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare A PR For NeMo Relay
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 at the end of a contributor or maintainer change before opening a pull request. Also use it whenever a user asks to create, open, publish, update, or edit a NeMo Relay pull request, pull request description, or PR body.
If this repo-local guidance conflicts with generic GitHub publishing, connector, or plugin guidance, this skill wins for PR body format, validation language, and review handoff details.
Checklist
- Branch scope is coherent and reviewable
- Relevant tests passed under
validate-change - Changed files were formatted with the language-native formatter
- Any Rust change ran
just test-rust - Any Rust change ran
cargo fmt --all - Any Rust change ran
cargo clippy --workspace --all-targets -- -D warnings -
crates/coreorcrates/adaptivechanges ran the full language matrix - Targeted
uv run pre-commit run --files <changed files...>checks were used during iteration where useful -
uv run pre-commit run --all-filespassed or issues are understood - Docs and examples updated for any public behavior changes
- Dependent maintainer or consumer skills updated when code changes affected their APIs, bindings, commands, paths, packaging guidance, or best practices
- Pull request title follows Conventional Commit style and uses the correct type
- Pull request body follows
.github/pull_request_template.md - Breaking changes or renamed surfaces are called out explicitly
Pull Request Title
Use Conventional Commit style for PR titles:
<type>: <concise imperative summary>
Choose the type from the actual change surface, not from the impact of the
review comment or CI outcome. Use fix only for an actual user-facing or
runtime/product code bug fix. Never use fix for changes that are not related
to product code behavior, including chores, CI configuration, docs, tests,
packaging metadata, generated-output handling, or agent/skill guidance.
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.
- 4d ago First seen · 111 lines · 39 tokens per session scan A 7f9ecc33b03a
prepare-pr is a skill published in the GitHub repository NVIDIA/NeMo-Relay (132 stars, last pushed 4d ago), licensed Apache-2.0. It adds 39 tokens to every session and 980 once invoked, about $0.0002 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
atifact
This skill should be used when the user asks to "extract agent trajectory", "convert HAR to trajectory", "get trajectory from session", "parse agent session", "convert Claude Code logs", "convert Copilot CLI logs", "extract ATIF", or needs to convert HAR files or JSONL session logs into ATIF trajectory JSON using the…
bump-version
This skill should be used when the user asks to "bump the version", "release a new version", "prepare a release", "update the version number", "version bump", or needs to determine and apply a semver version increment based on recent commits.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.