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-evening/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-evening)<a href="https://agentmods.dev/skills/nvidia/nemoclaw/nemoclaw-maintainer-evening"><img src="https://agentmods.dev/badge/skills/nvidia/nemoclaw/nemoclaw-maintainer-evening/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-evening"><img src="https://agentmods.dev/badge/skills/nvidia/nemoclaw/nemoclaw-maintainer-evening.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.00030 | $0.01117 |
| Opus 5.5 | $0.00012 | $0.00447 |
| Sonnet 5.5 | $0.00006 | $0.00223 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
nemoclaw-maintainer-evening 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NemoClaw Maintainer Evening
Close the day with one release candidate, one cumulative documentation change, and a clear handoff. Tagging is optional. Report tag creation first, then let the tag skill finish post-tag follow-through.
See PR-REVIEW-PRIORITIES.md for the daily cadence and the release-train policy for release rules.
1. Select the Target Version
Use the maintainer's vX.Y.Z when supplied. Otherwise, read the current target and show its
merged and open work:
node --no-warnings \
.agents/skills/nemoclaw-maintainer-day/scripts/version-target.ts
node --no-warnings \
.agents/skills/nemoclaw-maintainer-day/scripts/version-progress.ts vX.Y.Z
Do not silently convert the answer into a patch, minor, or major bump. If nothing shipped, ask whether to stop without a tag.
2. Finish One Cumulative Documentation Change
Start the release kickoff checks for the intended range. Report independent prerequisites together, and continue authorized docs preparation and review during image waits. These preliminary reads do not select the tag candidate.
Inspect the current Docs / Author Post-Merge Catch-Up state. The Pi workflow owns documentation catch-up
for merged changes. Continue its managed draft PR when one exists. If no managed PR exists and the
release entry is the only missing change, use one direct documentation-only PR.
The documentation PR must contain all required documentation for every merged change selected for
the release. Write or update the pre-tag changelog entry in docs/changelog/YYYY-MM-DD.mdx,
headed ## vX.Y.Z, within the cumulative documentation PR. Follow
docs/CONTRIBUTING.md and obtain its required independent
documentation writer review. Do not create a separate release-entry PR when the active cumulative
docs PR can carry it.
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 · +4 lines · -10 tokens per session 407f8c90ccb4
- 1mo ago Changed · +1 lines 6072b83be704
- 1mo ago Changed 927020a653d5
- 2mo ago First seen · 104 lines · 40 tokens per session scan A 7ae2d20cdf40
nemoclaw-maintainer-evening is a skill published in the GitHub repository NVIDIA/NemoClaw (22,871 stars, last pushed today), licensed Apache-2.0. It adds 30 tokens to every session and 1,117 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.
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
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.