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-morning/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-morning)<a href="https://agentmods.dev/skills/nvidia/nemoclaw/nemoclaw-maintainer-morning"><img src="https://agentmods.dev/badge/skills/nvidia/nemoclaw/nemoclaw-maintainer-morning/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-morning"><img src="https://agentmods.dev/badge/skills/nvidia/nemoclaw/nemoclaw-maintainer-morning.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.00080 | $0.00814 |
| Opus 5 | $0.00040 | $0.00407 |
| Sonnet 5 | $0.00016 | $0.00163 |
| Haiku 4.5 | $0.00008 | $0.00081 |
Grade A, and why
nemoclaw-maintainer-morning 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 2d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NemoClaw Maintainer Morning
Start the day: triage, pick a version target, label items, share the plan.
See PR-REVIEW-PRIORITIES.md for the daily cadence and review priorities.
Step 1: Determine Target Version and Stragglers
node --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/version-target.ts
This fetches tags, computes the next patch version, and finds open items still carrying older version labels. Surface stragglers first — they indicate post-tag housekeeping was interrupted or an item slipped across multiple cycles. Decide whether to relabel them to today's target or defer them out of the daily release flow.
Step 2: Triage
Run the triage script to rank the full backlog:
node --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/triage.ts --approved-only
If too few results, run without --approved-only. The script fetches open PRs through gh, reads Project 199 Priority, enriches candidates with review, CI, file, and risky-area data, and applies the scoring model documented in PR-REVIEW-PRIORITIES.md.
Also use find-review-pr to surface security PRs whose Project Priority is Urgent or High. Merge these into the candidate pool.
Step 3: Label Version Targets
Present the ranked queue to the user. After they confirm which items to target, label them:
gh label create "<version>" --repo NVIDIA/NemoClaw --description "Release target" --color "1d76db" 2>/dev/null || true
gh pr edit <number> --repo NVIDIA/NemoClaw --add-label "<version>"
gh issue edit <number> --repo NVIDIA/NemoClaw --add-label "<version>"
Step 4: Save State and Output the Plan
Pipe triage output into state:
node --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/triage.ts \
| node --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/state.ts set-queue
Output the daily plan:
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.
- 2d ago Changed fd14acc61a71
- 13d ago First seen · 67 lines · 80 tokens per session scan A 554331ee102d
nemoclaw-maintainer-morning is a skill published in the GitHub repository NVIDIA/NemoClaw (22,442 stars, last pushed today), licensed Apache-2.0. It adds 80 tokens to every session and 814 once invoked, about $0.0004 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
project-setup-info-local
Comprehensive setup steps to help the user create complete project structures in a VS Code workspace; this tool is designed for full project initialization and scaffolding, not for creating individual files. When to use this tool: user wants to create a new complete project from scratch; setting up entire project…
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
team-coordination
Use before deciding how you should organize team work: DAG vs Loop, dependency shape, task waves, quality gates, acceptance criteria, interruption, replanning, or what to do after Worker results arrive. Always use this skill for team organization strategy before you call project-management or task-management.
teamharness-task-delegation
Use when a Leader turns ready Quick Task or Project Work state into Worker task instructions, sends assignment messages, checks submitted results, and defines completion/blocker report contracts. Do not use to create projects, create rooms, or execute Worker tasks.