nemotron-policy-generator

nemotron-policy-generator is a skill for Claude Code, Codex from NVIDIA-NeMo/Nemotron. It costs 85 tokens per session (4,748 once invoked), scanned A, original, Apache-2.0.

A policy-writing aid for NVIDIA Nemotron content-safety models, which check text or images for unsafe material. It turns rough safety requirements or an existing policy into Markdown rules, a JSON category list, and prompts for model use.

In plain words
What is it for?
Use it to draft or extend safety, moderation, guardrail, labeling, or evaluation policies for chatbots, search systems, education, healthcare, finance, and code assistants.
Why use it?
It removes the need to turn informal requests such as “block weapons but allow medical content” into the model’s required structure by hand.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code.

Good fit Use it to draft or extend safety, moderation, guardrail, labeling, or evaluation policies for chatbots, search systems, education, healthcare, finance, and code assistants.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nvidia-nemo/nemotron/nemotron-policy-generator
About the project

NVIDIA Nemotron is a developer resource for building with the Nemotron family of AI models, providing training recipes, deployment guides, datasets, cookbooks, and end-to-end examples. It is intended for developers and researchers training, customizing, deploying, or applying Nemotron models to agentic AI use cases. Its catalogue add-ons include a Claude Code plugin that guides users through Nemotron customization steps.

NVIDIA-NeMo/Nemotron · 2,043 stars · on GitHub · docs.nvidia.com

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add NVIDIA-NeMo/Nemotron --skill nemotron-policy-generator
Clone the repo
git clone --depth 1 https://github.com/NVIDIA-NeMo/Nemotron

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for nemotron-policy-generator

README.md
[![agentmods](https://agentmods.dev/badge/skills/nvidia-nemo/nemotron/nemotron-policy-generator/github.svg)](https://agentmods.dev/skills/nvidia-nemo/nemotron/nemotron-policy-generator)
Your own site
<a href="https://agentmods.dev/skills/nvidia-nemo/nemotron/nemotron-policy-generator"><img src="https://agentmods.dev/badge/skills/nvidia-nemo/nemotron/nemotron-policy-generator/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.

agentmods 80×15 button for nemotron-policy-generator

Your own site · 80×15
<a href="https://agentmods.dev/skills/nvidia-nemo/nemotron/nemotron-policy-generator"><img src="https://agentmods.dev/badge/skills/nvidia-nemo/nemotron/nemotron-policy-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,748 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 123
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00085 $0.04748
Opus 5 $0.00043 $0.02374
Sonnet 5 $0.00017 $0.00950
Haiku 4.5 $0.00009 $0.00475

Measured 12d ago against content hash 5c9cb78cca6b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

nemotron-policy-generator 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 12d 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.

skills/nemotron-policy-generator/SKILL.md · 223 lines

How it starts

The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Nemotron Policy Generator

When to Use This Skill

Activate this skill whenever the user asks for help producing a content-safety policy for NVIDIA Nemotron safety models. Concretely:

  • The user mentions any of: NCS, NCS-VL, NCS-Reasoning, Nemotron Content Safety, NeMo Guardrails, Aegis taxonomy.
  • The user asks to "build", "draft", "generate", "expand", or "extend" a safety policy, content policy, moderation policy, guardrail config, BYO-policy, custom safety taxonomy, eval rubric, or labeling rubric.
  • The user describes their needs in rough words ("no weapons, allow medical, block hate speech") and expects a structured artifact back.
  • The user names a deployment context (consumer chat, enterprise RAG, kids/edu, healthcare, financial, code assistant, sovereign deployment) and asks for the safety rules that fit.

Do not activate this skill when:

  • The user wants to evaluate an existing policy's quality, not generate one — that's a review task.
  • The user wants to test whether NCS follows a policy — that's an eval/benchmark task; defer to a benchmark/eval skill.
  • The user is asking for legal advice on what their policy should cover — defer; this skill generates artifacts from user-supplied intent, it doesn't decide what's legally required in a jurisdiction.

What This Skill Produces

From any rough input, this skill produces a structured, internally consistent policy in the formats Nemotron consumes:

  • Markdown policy — the canonical, sign-off-ready source of truth; everything else derives from it.
  • JSON taxonomy — schema-validated structured form for downstream tooling.
  • Nemotron system prompt — drop-in classification prompt for NCS / NCS-VL / NCS-Reasoning.
  • Word doc (.docx) — only if the user explicitly asks or mentions sign-off / legal / review.

Read the full file on GitHub · 223 lines

Changes

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.

  1. 12d ago First seen · 223 lines · 85 tokens per session scan A 5c9cb78cca6b

Subscribe to this mod's changes

nemotron-policy-generator is a skill published in the GitHub repository NVIDIA-NeMo/Nemotron (2,043 stars, last pushed 5d ago), licensed Apache-2.0. It adds 85 tokens to every session and 4,748 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.

Related

Other skills, from other repositories

tinker-fine-tuning

Provides guidance for fine-tuning LLMs using the Tinker cloud training API from Thinking Machines Lab. Use when running supervised fine-tuning, reinforcement learning (GRPO/PPO), or LoRA training on cloud GPUs via Tinker's managed infrastructure instead of local compute.

synthetic-sciences/openscience · 62 tokens

fine-tuning-with-trl

Fine-tune LLMs using reinforcement learning with TRL - SFT for instruction tuning, DPO for preference alignment, PPO/GRPO for reward optimization, and reward model training. Use when need RLHF, align model with preferences, or train from human feedback. Works with HuggingFace Transformers.

davila7/claude-code-templates · 69 tokens

huawei-cloud-cloudrobo-train

Manage CloudRobo model training tasks and simulation reinforcement learning (SimRL) tasks — create pretrain (TRAINFROMSCRATCH) and finetune (MODELTUNING) tasks with FFT/SFT/LORA/QLORA/DEEPSPEED methods; manage the full task lifecycle (create/read/update/delete/stop/restart/resume/draft); save and resubmit draft…

huaweicloud/huaweicloud-skills · 264 tokens

fine-tuning-with-trl

Fine-tune LLMs using reinforcement learning with TRL - SFT for instruction tuning, DPO for preference alignment, PPO/GRPO for reward optimization, and reward model training. Use when need RLHF, align model with preferences, or train from human feedback. Works with HuggingFace Transformers.

OpenLAIR/dr-claw · 69 tokens

fine-tuning-with-trl

Fine-tune LLMs using reinforcement learning with TRL - SFT for instruction tuning, DPO for preference alignment, PPO/GRPO for reward optimization, and reward model training. Use when need RLHF, align model with preferences, or train from human feedback. Works with HuggingFace Transformers.

Orchestra-Research/AI-Research-SKILLs · 69 tokens

fine-tuning-with-trl

Fine-tune LLMs using reinforcement learning with TRL - SFT for instruction tuning, DPO for preference alignment, PPO/GRPO for reward optimization, and reward model training. Use when need RLHF, align model with preferences, or train from human feedback. Works with HuggingFace Transformers.

liortesta/ClawdAgent · 69 tokens