NVIDIA/NemoClaw is an open-source reference stack for running supported AI agents inside NVIDIA OpenShell sandboxes with managed inference, network policies, integrations, snapshots, and lifecycle controls. It is used to run agents such as OpenClaw, Hermes, and LangChain Deep Agents with administrative and security controls. Catalogue add-ons guide coding agents through NemoClaw workflows.
Borrowing it
Nothing to install: this file belongs to NVIDIA/NemoClaw. 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/NemoClaw/main/.agents/skills/nemoclaw-maintainer-security-code-review/SKILL.mdgit clone --depth 1 https://github.com/NVIDIA/NemoClawWrote 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/nemoclaw/nemoclaw-maintainer-security-code-review)<a href="https://agentmods.dev/skills/nvidia/nemoclaw/nemoclaw-maintainer-security-code-review"><img src="https://agentmods.dev/badge/skills/nvidia/nemoclaw/nemoclaw-maintainer-security-code-review/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/nemoclaw/nemoclaw-maintainer-security-code-review"><img src="https://agentmods.dev/badge/skills/nvidia/nemoclaw/nemoclaw-maintainer-security-code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- 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.00078 | $0.01070 |
| Opus 5 | $0.00039 | $0.00535 |
| Sonnet 5 | $0.00016 | $0.00214 |
| Haiku 4.5 | $0.00008 | $0.00107 |
Grade A, and why
nemoclaw-maintainer-security-code-review 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 10d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Code Review
Review the changes in a GitHub PR for security. An issue input must identify one open linked PR. Report a verdict for each category.
Prerequisites
gh(GitHub CLI) must be installed and authenticated.gitmust be available.- Network access to clone repositories and fetch PR metadata.
Step 1: Parse the GitHub URL
If the user gives a PR or issue URL, extract the owner, repository, and number. Otherwise, ask for the URL.
Supported URL formats:
https://github.com/OWNER/REPO/pull/NUMBERhttps://github.com/OWNER/REPO/issues/NUMBER
For a PR URL, verify the number before Step 2:
gh pr view <number> --repo OWNER/REPO --json number,url
For an issue URL, list its open closing PRs:
gh issue view <number> --repo OWNER/REPO --json closedByPullRequestsReferences \
--jq '.closedByPullRequestsReferences | map(select(.state == "OPEN")) | .[].number'
Continue only when this returns one PR number, and verify that number with gh pr view.
If it returns zero or more than one, stop and ask for the PR URL.
Use the verified PR number in each later command.
Step 2: Check Out the Code
Compare gh repo view --json nameWithOwner -q .nameWithOwner with the URL.
If the repositories match, check out the verified PR:
gh pr checkout <number>
If the repositories do not match, clone the target to a temporary directory:
REVIEW_DIR=$(mktemp -d)
gh repo clone OWNER/REPO "$REVIEW_DIR"
cd "$REVIEW_DIR"
gh pr checkout <number>
Step 3: Identify Changed Files
List all files changed from the base branch:
git diff main...HEAD --name-status
If the PR targets another branch, use that branch as the base. Check it with:
gh pr view <number> --json baseRefName -q .baseRefName
Step 4: Read Each Changed File and Diff
Read each changed file. Read its diff:
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.
- 10d ago First seen · 141 lines · 78 tokens per session scan A f1ba07af9ddb
nemoclaw-maintainer-security-code-review is a skill published in the GitHub repository NVIDIA/NemoClaw (22,418 stars, last pushed yesterday), licensed Apache-2.0. It adds 78 tokens to every session and 1,070 once invoked, about $0.0004 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
pentest-whitebox-code-review
Source code security audit using backward taint analysis, slot type classification, render context verification, and 3-phase parallel review producing an exploitation queue.
triage-contributor-pr
Triage open pull requests from external contributors to prisma/prisma and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
update-pr
Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.
remember
Review the current conversation and capture valuable knowledge — best practices, coding conventions, architecture decisions, workflows, and user feedback — into persistent memory (AGENTS.md) or reusable skills. Use when the user says: (1) remember this, (2) save what we learned, (3) update memory, (4) capture…
code-review
Perform a structured code review of changes, checking for correctness, style, tests, and potential issues.