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/create-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/create-pr)<a href="https://agentmods.dev/skills/nvidia-nemo/datadesigner/create-pr"><img src="https://agentmods.dev/badge/skills/nvidia-nemo/datadesigner/create-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/create-pr"><img src="https://agentmods.dev/badge/skills/nvidia-nemo/datadesigner/create-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.00035 | $0.01640 |
| Opus 5.5 | $0.00014 | $0.00656 |
| Sonnet 5.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 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 — 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.
- 1mo 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,366 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 1,640 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.