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/datadesigner/review-codenpx skills add NVIDIA-NeMo/DataDesigner --skill review-codegit clone --depth 1 https://github.com/NVIDIA-NeMo/DataDesignerWhat 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.00020 | $0.04378 |
| Opus 5 | $0.00010 | $0.02189 |
| Sonnet 5 | $0.00004 | $0.00876 |
| Haiku 4.5 | $0.00002 | $0.00438 |
Grade A, and why
review-code 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.
How it starts
The opening of the file, as written. The whole thing — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Code Changes
Perform a comprehensive code review of either the current branch or a specific GitHub pull request.
Arguments
$ARGUMENTS determines the review mode:
PR mode — first argument is a number:
366— review PR #366366 focus on the API changes— review PR #366 with a focus area
Branch mode — no number, or only instructions:
- (empty) — review current branch against
main compare against develop— review against a different basefocus on the API changes— review current branch with a focus area
Additional instructions work in both modes:
be strict about type annotationsskip style nits
Step 1: Gather Changes
If PR mode (argument starts with a number)
Run these commands in parallel using gh:
- PR details:
gh pr view <number> --json title,body,author,baseRefName,headRefName,state,additions,deletions,changedFiles,commits,url - PR diff:
gh pr diff <number> - PR files:
gh pr diff <number> --name-only - PR commits:
gh pr view <number> --json commits --jq '.commits[].messageHeadline' - Existing inline review comments:
gh api repos/{owner}/{repo}/pulls/<number>/comments --paginate --jq '.[].body'5b. Existing PR-level reviews (top-level review bodies from "Review changes"):gh api repos/{owner}/{repo}/pulls/<number>/reviews --paginate --jq '.[].body' - Repo info:
gh repo view --json nameWithOwner -q '.nameWithOwner'
Then get the PR branch locally for full file access. Prefer a worktree so your current branch and uncommitted work are untouched:
git fetch origin pull/<number>/head:pr-<number> --force
git worktree add /tmp/review-<number> pr-<number>
# Cleanup when done: git worktree remove /tmp/review-<number> && git branch -D pr-<number>
If worktrees aren't suitable, you can use gh pr checkout <number> (this switches your current branch — only if you have no uncommitted work). Run the rest of the review from /tmp/review-<number>.
If checkout isn't possible (e.g., external fork), use gh api to fetch file contents:
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.
- 2d ago First seen · 348 lines · 20 tokens per session scan A fc3d0bb30c38
review-code is a skill published in the GitHub repository NVIDIA-NeMo/DataDesigner (2,194 stars, last pushed 3d ago), licensed Apache-2.0. It adds 20 tokens to every session and 4,378 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
omni-rewriter-promo-pipeline
Build Omni-Rewriter promo films: validated H3 PE chunks, RAW vs PE proof cards with PE audio, designed models finale, and soft-xfade assemble. Use when making or regenerating docs/promo media, promo scripts, or agent workflows that mirror the maintainer promo pipeline.
omni-rewriter-model-contribution
Scaffold and review new Video, Image, or Unified model contributions for Omni-Rewriter. Use when adding a PE profile, task route, validator, renderer, fixture, generation adapter, compatibility claim, or model-support pull request.
omni-rewriter-h3-pe
Extend Omni-Rewriter's validated prompt-expansion framework and its H3 video and Seedream / Qwen-Image image profiles. Use when writing profile rules, RewriteRequest fixtures, PE repairs, renderers, adapters, or raw-vs-expanded comparisons.
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
evolve
Start or monitor an evolutionary development loop.