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-policies/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-policies)<a href="https://agentmods.dev/skills/nvidia/nemoclaw/nemoclaw-maintainer-policies"><img src="https://agentmods.dev/badge/skills/nvidia/nemoclaw/nemoclaw-maintainer-policies/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-policies"><img src="https://agentmods.dev/badge/skills/nvidia/nemoclaw/nemoclaw-maintainer-policies.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.00034 | $0.00518 |
| Opus 5.5 | $0.00014 | $0.00207 |
| Sonnet 5.5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
nemoclaw-maintainer-policies 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NemoClaw Maintainer Policies
This package contains policy references. This file is its manifest and index.
References
Read the reference that owns the question. Read additional references only when that question crosses their boundaries.
- references/workflow-policy.md — Source of truth, authorization, Issue Type, label boundaries, and agent-owned labels.
- references/triage-instructions.md — Issue and PR evaluation, questions,
needs:*, confidence, and suggestion payloads. - references/label-taxonomy.md — Label meaning, selection, compatibility, unknown labels,
agt: *, and release labels. - references/label-taxonomy.json — Allowed machine values and write policy.
- references/project-workflow.md — Project Status, lifecycle, duplicates, blocked work, review, and QA.
- references/daily-flow.md — Daily priorities, standup, assignment, execution, and QA handoff.
- references/release-train.md — Release inclusion, cutoff, carry-forward, history, and label retirement.
- references/examples.md — Examples for triage, review, release activation, competing PRs, and stale PRs.
Answering Workflow Questions
Read the related reference before you answer or apply policy.
Use plain language for maintainers. Distinguish Issue Type, PR type labels, needs:* labels, Project fields, close reasons, and release labels.
Do not invent labels, statuses, fields, release labels, or workflow states.
Follow the shared Documentation Writing and Review
contract for changed workflow guidance and maintainer-facing text.
For agent implementation, use triage-instructions.md as the payload contract.
Use label-taxonomy.json to validate allowed values.
What ships with it
8 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.
- 1mo ago Changed · -1 lines · -56 tokens per session a5b25f9546ab
- 2mo ago First seen · 40 lines · 90 tokens per session scan A e66806f623a0
nemoclaw-maintainer-policies is a skill published in the GitHub repository NVIDIA/NemoClaw (22,871 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 518 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
summarize-releases
Create a monthly NVIDIA Elements “What’s New” docs page, matching video, and concise, copy-ready summary from local release tags, tagged changelogs, package versions, and commit history. Use for a scheduled release PR, monthly update, release roundup, changelog digest, Slack blurb, announcement, or plain-language…
implement
Implement a Jira ticket — fetches ticket, checks for existing plan, creates worktree branch, runs implementation with verification. Usage - /implement IN-XXX.
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.