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.
Borrowing it
Nothing to install: this file belongs to NVIDIA/NeMo-Relay. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/NVIDIA/NeMo-Relay/main/.agents/skills/review-doc-style/SKILL.mdgit 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/review-doc-style)<a href="https://agentmods.dev/skills/nvidia/nemo-relay/review-doc-style"><img src="https://agentmods.dev/badge/skills/nvidia/nemo-relay/review-doc-style/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/review-doc-style"><img src="https://agentmods.dev/badge/skills/nvidia/nemo-relay/review-doc-style.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.00035 | $0.00371 |
| Opus 5.5 | $0.00014 | $0.00148 |
| Sonnet 5.5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
review-doc-style 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 1mo 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.
What it actually says
Review Documentation Style
Prioritize factual accuracy over copy polish. Confirm commands, package names, APIs, paths, supported bindings, and public behavior against the current repository before reporting style findings.
Review Flow
- Identify the changed documentation, examples, or public strings and any
corresponding entry points such as
README.md,docs/index.yml, or package READMEs. - Read
references/nvidia-style-guide.mdfor the fast-path checklist and severity model. - Open only the focused reference that resolves an actual ambiguity:
references/nvidia-style-technical-docs.mdfor structure, procedures, examples, links, tables, UI text, or accessibility.references/nvidia-style-language-mechanics.mdfor voice, grammar, punctuation, dates, numbers, units, or plain English.references/nvidia-style-brand-terminology.mdfor NVIDIA and product names, trademarks, acronyms, legal copy, or SEO.
- Verify MDX files use JSX delimiters for top-of-file SPDX comments.
- Report findings in severity order with a file and line, reader impact, and a concrete rewrite or direction. Omit preference-only findings unless the user requested a deep copyedit.
If no issues are found, say so and identify any commands or examples that were not executed.
References
CONTRIBUTING.mdreferences/nvidia-style-guide.md- Open only the focused NVIDIA style reference selected in step 3.
What ships with it
4 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.
- 1mo ago Changed · -79 lines · +11 tokens per session 4f2ada4802fb
- 1mo ago First seen · 119 lines · 24 tokens per session scan A 64eb4446c6e3
review-doc-style is a skill published in the GitHub repository NVIDIA/NeMo-Relay (212 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 371 once invoked, about $0.0001 per session on Opus 5.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
migration-review
Review database migration files when a change adds or modifies paths under migrations/. Use it before merge to collect forward, rollback, locking, and data-safety evidence.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
learn-from-sage
Detection-gap (miss) analysis for Code Review Sage. Learn from shipped fixes, acted-on human comments, and design outcomes to close reviewer blind spots. Inline during review stages a candidate; a human triggers a one-shot AI consolidation into the live ruleset.
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
factory-gitlab-rereview
Re-review a GitLab merge request after new commits and reconcile the previous review.