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-release-notes/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-release-notes)<a href="https://agentmods.dev/skills/nvidia/nemoclaw/nemoclaw-maintainer-release-notes"><img src="https://agentmods.dev/badge/skills/nvidia/nemoclaw/nemoclaw-maintainer-release-notes/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-release-notes"><img src="https://agentmods.dev/badge/skills/nvidia/nemoclaw/nemoclaw-maintainer-release-notes.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.00041 | $0.01908 |
| Opus 5 | $0.00020 | $0.00954 |
| Sonnet 5 | $0.00008 | $0.00382 |
| Haiku 4.5 | $0.00004 | $0.00191 |
Grade A, and why
nemoclaw-maintainer-release-notes 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NemoClaw Maintainer Release Notes
Draft the post-tag NemoClaw Announcement from GitHub tag and compare data. The house style is:
- three narrative lead paragraphs,
- a categorized list of shipped changes,
- one bullet for each shipped change that states what changed and why it matters,
- external-only contributor thanks,
- visible
#NNNNGitHub links.
Follow the shared Documentation Writing and Review contract for new or modified Announcement text. State the changed behavior, affected users, and required action when one exists. Do not rewrite unrelated historical release text.
Create a local Markdown draft. Do not create or update a GitHub Discussion; the maintainer posts the announcement manually.
Prerequisites
- You must be in the NemoClaw git repository.
ghmust be authenticated forNVIDIA/NemoClaw.- The release tag should already exist. If the user is still cutting the tag, use
nemoclaw-maintainer-cut-release-tagfirst. - The tagged commit should already contain exactly one
## <current-version>entry indocs/changelog/YYYY-MM-DD.mdx. This skill drafts the post-tag Announcement and does not replace or create that canonical entry. - Use live GitHub and remote tag state, not memory or a stale local branch.
- Read the signed tag annotation or its
release-brief.mdsource for release-range facts. Do not copy internal test results or exception details into the public Announcement.
Step 1: Verify the Release Range
Identify the current release tag and previous release tag. If the user gives only the current version, derive the previous semver tag from remote tags.
git ls-remote https://github.com/NVIDIA/NemoClaw.git \
refs/heads/main \
refs/tags/<previous-version> 'refs/tags/<previous-version>^{}' \
refs/tags/<current-version> 'refs/tags/<current-version>^{}'
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 · 189 lines · 41 tokens per session scan A cfbef526ac75
nemoclaw-maintainer-release-notes is a skill published in the GitHub repository NVIDIA/NemoClaw (22,418 stars, last pushed today), licensed Apache-2.0. It adds 41 tokens to every session and 1,908 once invoked, about $0.0002 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
publish-npm-packages
Configure, audit, or migrate npm package publishing to current secure practices. Use when Codex needs to publish or prepare an npm package, fill npm Trusted Publisher settings, create a GitHub Actions/GitLab/CircleCI release workflow, adopt OIDC, replace npm tokens, publish organization-scoped public or private…
backup
Backup and restore openclaw configuration, skills, commands, and settings. Sync across devices, version control with git, automate backups, and migrate to new machines.
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
generate-run-commands
Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.