NVIDIA-NeMo/DataDesigner is a framework for generating synthetic datasets from scratch or from seed data, including text, structured records and images, while controlling field relationships and validating results. Data scientists and developers use it to create and evaluate data-generation workflows that can include models, seed datasets, external tools and custom validators. The catalogue entries provide agent skills, agents, instructions and settings for working with Data Designer.
Borrowing it
Nothing to install: this file belongs to NVIDIA-NeMo/DataDesigner. 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-NeMo/DataDesigner/main/.agents/skills/update-pr/SKILL.mdgit clone --depth 1 https://github.com/NVIDIA-NeMo/DataDesignerWrote 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-nemo/datadesigner/update-pr)<a href="https://agentmods.dev/skills/nvidia-nemo/datadesigner/update-pr"><img src="https://agentmods.dev/badge/skills/nvidia-nemo/datadesigner/update-pr/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-nemo/datadesigner/update-pr"><img src="https://agentmods.dev/badge/skills/nvidia-nemo/datadesigner/update-pr.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.00017 | $0.01228 |
| Opus 5.5 | $0.00007 | $0.00491 |
| Sonnet 5.5 | $0.00003 | $0.00246 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade A, and why
update-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 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Pull Request
Update the description of an existing GitHub pull request for the current branch.
Arguments
$ARGUMENTS can be used for:
--titleflag: Include to also update the PR title- Special instructions (same as create-pr):
- Guiding the summary: "emphasize the performance improvements"
- Adding context: "this PR now also includes the auth fixes"
- Any other guidance for the updated description
Step 1: Find the Existing PR
- Get current branch and PR info:
gh pr view --json number,title,body,url,headRefName,state
Important checks:
- If no PR exists for the current branch, fail and inform the user to use
/create-prinstead - If the PR is merged or closed, fail and inform the user the PR is no longer open
Step 2: Gather Current State
Run these commands in parallel to understand the full state:
- Uncommitted changes:
git status --porcelain - All 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 - 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
Step 3: Analyze and Categorize Changes
By Change Type (from commits and diff)
- ✨ Added: New files, features, capabilities
- 🔧 Changed: Modified existing functionality
- 🗑️ Removed: Deleted files or features
- 🐛 Fixed: Bug fixes
- 📚 Docs: Documentation updates
- 🧪 Tests: Test additions/modifications
Identify Attention Areas
Flag for special reviewer attention:
- Files with significant changes (>100 lines)
- Changes to base classes, interfaces, or public API
- New dependencies (
pyproject.toml,requirements.txt) - Configuration schema changes
- Security-related changes
Step 4: Update the PR
- Push any new commits (if needed):
git push
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 First seen · 152 lines · 17 tokens per session scan A 7bd8fc3714b9
update-pr is a skill published in the GitHub repository NVIDIA-NeMo/DataDesigner (2,366 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 1,228 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
apply-patch
Apply multi-file or tricky edits atomically with git apply instead of many fragile editfile calls. Use when changing several files at once or when editfile fails to match.
git-checkpoint
Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.
commit
Create git commits with good messages. Use when user says "commit", "create commit", or asks to commit changes.
public-plugin-packaging
Use when packaging an Agentlas agent repo for public GitHub release, Codex plugin submission, Claude adapter distribution, or one-line terminal installation.
release-notes
Write release notes for a tagged release — a business-impact summary of what changed for the user, plus a thanks section naming every contributor whose commits are in the release. Short by construction.
review-this-branch
Run the nohuman review gate (fresh-session adversarial reviewer + tamper guard) over the current branch or a GitHub pull request, with no server, no database, and no onboarding, and relay the pass/fail checklist.