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-contributor-update-dependencies/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-contributor-update-dependencies)<a href="https://agentmods.dev/skills/nvidia/nemoclaw/nemoclaw-contributor-update-dependencies"><img src="https://agentmods.dev/badge/skills/nvidia/nemoclaw/nemoclaw-contributor-update-dependencies/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-contributor-update-dependencies"><img src="https://agentmods.dev/badge/skills/nvidia/nemoclaw/nemoclaw-contributor-update-dependencies.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.00106 | $0.01110 |
| Opus 5 | $0.00053 | $0.00555 |
| Sonnet 5 | $0.00021 | $0.00222 |
| Haiku 4.5 | $0.00011 | $0.00111 |
Grade A, and why
nemoclaw-contributor-update-dependencies 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 yesterday.
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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Dependencies
Treat an upgrade as a migration, not a version edit. Explain the changed upstream contracts, their NemoClaw consumers, the required migrations, and the evidence for each conclusion.
Load this workflow from nemoclaw-contributor-implement-issue for a dependency upgrade.
nemoclaw-contributor-implement-issue still owns issue scope and handoff; this workflow owns the
upgrade procedure.
Mutation boundary
Change only the NVIDIA/NemoClaw checkout in scope. Treat upstream repositories, registries, workflows, issue trackers, and PRs as read-only. Report an upstream defect and its downstream effect. Require a separate user request for upstream changes.
Plan the upgrade
Add these outcomes to the working plan:
- Resolve the current and target source and artifact identities.
- Audit every adjacent release range.
- Map changed upstream contracts to current downstream consumers.
- Record security, lifecycle, state, packaging, and compatibility concerns.
- Implement required migrations before changing the final selector.
- Add concern-specific tests and runtime evidence.
- Verify the artifacts and selectors used by the PR head.
An unresolved high-impact concern blocks the upgrade.
Discover current contracts
Follow Discover the Current Implementation.
Search from the current dependency identity and each changed upstream identifier. Trace consumers through source, tests, configuration, generated inputs, packaging, workflows, and documentation. Do not maintain a path or selector inventory in this skill.
Audit upstream changes
For each adjacent release range:
- Resolve immutable source identities and publication status.
- Read the complete commit and changed-path inventory.
- Inspect source and upstream tests for plausible contract changes.
- Use release notes and PR descriptions as leads, not behavior authority.
- Compare resolved dependency graphs and distributed artifacts.
- Open a concern for each downstream effect or evidence-backed exclusion.
What ships with it
7 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.
- yesterday Changed · -7 lines d33f61f45908
- 11d ago First seen · 119 lines · 106 tokens per session scan A d256cb18533b
nemoclaw-contributor-update-dependencies is a skill published in the GitHub repository NVIDIA/NemoClaw (22,427 stars, last pushed today), licensed Apache-2.0. It adds 106 tokens to every session and 1,110 once invoked, about $0.0005 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
update-skills
Create or update repository skills and instructions when major learnings are discovered during a session. Use when the user says "learn!", when a significant pattern or pitfall is identified, or when reusable domain knowledge should be captured for future sessions.
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.
commit
Commit staged or unstaged changes with an AI-generated commit message that matches the repository's existing commit style. Use when the user asks to 'commit', 'commit changes', 'create a commit', 'save my work', or 'check in code'.
sync
Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.
merge
Merge changes from the topic branch to the merge base branch. Use when the user wants to merge their session's work back to the base branch.
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…