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.
npx agentmods add skills/nvidia-nemo/datadesigner/create-prnpx skills add NVIDIA-NeMo/DataDesigner --skill create-prgit clone --depth 1 https://github.com/NVIDIA-NeMo/DataDesignerWhat 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 | $0.00035 | $0.01640 |
| Opus 5 | $0.00017 | $0.00820 |
| Sonnet 5 | $0.00007 | $0.00328 |
| Haiku 4.5 | $0.00003 | $0.00164 |
Grade A, and why
create-pr 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 3d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request
Create a well-formatted GitHub pull request for the current branch. The PR description must conform to the repository's PR template (.github/PULL_REQUEST_TEMPLATE.md).
Arguments
$ARGUMENTS can be used for special instructions, such as:
- Specifying a base branch: "use base branch: develop"
- Guiding the summary: "emphasize the performance improvements in the summary"
- Adding context: "this is part of the auth refactor epic"
- Any other guidance for PR creation
Default base branch: main (unless specified in arguments)
Step 1: Gather Information
Run these commands in parallel to understand the changes:
- Current branch:
git branch --show-current - Uncommitted changes:
git status --porcelain - Commits on branch:
git log origin/main..HEAD --oneline - File changes summary:
git diff --stat origin/main..HEAD - Full diff:
git diff origin/main..HEAD - Recent commit style:
git log -5 --oneline(to match PR title convention) - Repo info:
gh repo view --json nameWithOwner -q '.nameWithOwner'(for constructing file URLs)
Important checks:
- If uncommitted changes exist, warn the user and ask if they want to commit first
- If no commits ahead of main, inform the user there's nothing to PR
- If branch isn't pushed, you'll push it in Step 4
Step 2: Analyze and Categorize Changes
Use change types below to decide how to write the Changes section (flat vs grouped). You still describe testing under Testing, not under these buckets.
By change type (internal checklist)
- ✨ Added: New files, features, capabilities
- 🔧 Changed: Modified existing functionality
- 🗑️ Removed: Deleted files or features
- 🐛 Fixed: Bug fixes
- 📚 Docs: Documentation updates
- 🧪 Tests: Test additions/modifications
When to use optional grouping in Changes
- Flat bullet list (default): Small PRs, single theme, or when categories would be sparse or redundant.
- Grouped subheadings (
### ✨ Added,### 🔧 Changed,### 🗑️ Removed,### 🐛 Fixed): Large PRs, release-note-style summaries, or clearly distinct fix + feature mixes. Omit any empty section — do not leave placeholder headings.
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.
- 3d ago First seen · 176 lines · 35 tokens per session scan A 53a84f4767fd
create-pr is a skill published in the GitHub repository NVIDIA-NeMo/DataDesigner (2,194 stars, last pushed 4d ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,640 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
omni-rewriter-promo-pipeline
Build Omni-Rewriter promo films: validated H3 PE chunks, RAW vs PE proof cards with PE audio, designed models finale, and soft-xfade assemble. Use when making or regenerating docs/promo media, promo scripts, or agent workflows that mirror the maintainer promo pipeline.
omni-rewriter-model-contribution
Scaffold and review new Video, Image, or Unified model contributions for Omni-Rewriter. Use when adding a PE profile, task route, validator, renderer, fixture, generation adapter, compatibility claim, or model-support pull request.
omni-rewriter-h3-pe
Extend Omni-Rewriter's validated prompt-expansion framework and its H3 video and Seedream / Qwen-Image image profiles. Use when writing profile rules, RewriteRequest fixtures, PE repairs, renderers, adapters, or raw-vs-expanded comparisons.
codemap
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping.
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.