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-docs/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-docs)<a href="https://agentmods.dev/skills/nvidia/nemoclaw/nemoclaw-contributor-update-docs"><img src="https://agentmods.dev/badge/skills/nvidia/nemoclaw/nemoclaw-contributor-update-docs/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-docs"><img src="https://agentmods.dev/badge/skills/nvidia/nemoclaw/nemoclaw-contributor-update-docs.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.00033 | $0.00719 |
| Opus 5.5 | $0.00013 | $0.00288 |
| Sonnet 5.5 | $0.00007 | $0.00144 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
nemoclaw-contributor-update-docs 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Documentation from Changes
Update documentation from current behavior. Use checked-in source, tests, and accepted product scope as behavior authority.
Establish the range
For Docs / Author Post-Merge Catch-Up, inspect changes from the latest reachable semver tag through the
exact pushed main commit. Do not advance either boundary while authoring. For a direct
documentation task, use the commit range supplied by the user or current checkout context.
Release-entry completion belongs to nemoclaw-maintainer-evening, not this workflow.
For an existing managed draft, extend its staged changes after the workflow merges them with main.
Preserve previous documentation changes unless current source and tests justify a revision or removal.
The independent reviewer checks those revisions against the previous draft commit.
Load current authority
Follow Discover the Current Implementation.
Read the active documentation guidance, the shared Documentation Writing and Review contract, and the current documentation navigation. Read the repository documentation skip file when it exists. Apply its current exclusions and prohibited terms.
Do not duplicate writing rules, page ownership, route conventions, agent variants, changelog format, or validation commands in this skill. Derive them from the current documentation guidance, source tree, package scripts, and workflows.
Find documentation impact
For each candidate change:
- Read the commit and PR context.
- Decide whether supported user-visible behavior changed.
- Verify the behavior in current source and tests.
- Confirm accepted product scope for every support claim.
- Find the owning page by searching current terminology, commands, configuration keys, errors, navigation, and recent documentation history.
- Inspect every applicable guide variant before editing shared content.
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 · -38 tokens per session 77aef5fe3e62
- 1mo ago Changed · +4 lines 5c3103a00399
- 2mo ago First seen · 72 lines · 71 tokens per session scan A 4faf60a3bb97
nemoclaw-contributor-update-docs is a skill published in the GitHub repository NVIDIA/NemoClaw (22,871 stars, last pushed today), licensed Apache-2.0. It adds 33 tokens to every session and 719 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
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.
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.
contrib-pr
Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.
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.