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/data-designernpx skills add NVIDIA-NeMo/DataDesigner --skill data-designergit 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/data-designer)<a href="https://agentmods.dev/skills/nvidia-nemo/datadesigner/data-designer"><img src="https://agentmods.dev/badge/skills/nvidia-nemo/datadesigner/data-designer.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00025 | $0.01061 |
| Opus 5 | $0.00013 | $0.00531 |
| Sonnet 5 | $0.00005 | $0.00212 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
data-designer 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 4d 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.
This is a copy
100% identical to data-designer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before You Start
Do not explore the workspace first. The workflow's Learn step gives you everything you need.
Goal
Build a synthetic dataset using the Data Designer library that matches this description:
$ARGUMENTS
Workflow
Use Autopilot mode if the user implies they don't want to answer questions — e.g., they say something like "be opinionated", "you decide", "make reasonable assumptions", "just build it", "surprise me", etc. Otherwise, use Interactive mode (default).
Read only the workflow file that matches the selected mode, then follow it:
- Interactive → read
workflows/interactive.md - Autopilot → read
workflows/autopilot.md
Rules
- Keep all columns in the output by default. The only exceptions for dropping a column are: (1) the user explicitly asks, or (2) it is a helper column that exists solely to derive other columns (e.g., a sampled person object used to extract name, city, etc.). When in doubt, keep the column.
- Do not suggest or ask about seed datasets. Only use one when the user explicitly provides seed data or asks to build from existing records. When using a seed, read
references/seed-datasets.md. - When the dataset requires person data (names, demographics, addresses), read
references/person-sampling.md. - If a dataset script that matches the dataset description already exists, ask the user whether to edit it or create a new one.
Usage Tips and Common Pitfalls
- Sampler and validation columns need both a type and params. E.g.,
sampler_type="category"withparams=dd.CategorySamplerParams(...). - Jinja2 templates in
prompt,system_prompt, andexprfields: reference columns with{{ column_name }}, nested fields with{{ column_name.field }}. SamplerColumnConfig: Takesparams, notsampler_params.- LLM judge score access:
LLMJudgeColumnConfigproduces a nested dict where each score name maps to{reasoning: str, score: int}. To get the numeric score, use the.scoreattribute. For example, for a judge column namedqualitywith a score namedcorrectness, use{{ quality.correctness.score }}. Using{{ quality.correctness }}returns the full dict, not the numeric score.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- BENCHMARK.md 3.7 KB
- evals/evals.json 1.4 KB
- references/person-sampling.md 2.3 KB
- references/preview-review.md 1.8 KB
- references/seed-datasets.md 1.1 KB
- scripts/get_person_object_schema.py 1.7 KB runs code
- skill-card.md 3.6 KB
- skill.oms.sig 5.9 KB
- workflows/autopilot.md 2.6 KB
- workflows/interactive.md 3.2 KB
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.
- 4d ago First seen · 95 lines · 25 tokens per session scan A 30aeee1ecb4a
data-designer is a skill published in the GitHub repository NVIDIA-NeMo/DataDesigner (2,198 stars, last pushed today), licensed Apache-2.0. It adds 25 tokens to every session and 1,061 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to data-designer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
community-research-insight
Extract structured insight briefs from community research transcripts or notes. Produces pain points, stakeholder needs, opportunity maps, risks, and follow-up questions. Requires human review before publication.
history-explorer
Inspect recent session conversation turns and meta-run history. Returns structured JSON summaries of turn counts, role distribution, tool usage, meta-skill executions, and co-occurrence patterns. Use this before running meta-skill-creator or when the user asks about recent history, past tool usage, or session activity.
llama-factory
Expert guidance for fine-tuning LLMs with LLaMA-Factory - WebUI no-code, 100+ models, 2/3/4/5/6/8-bit QLoRA, multimodal support.
screenpipe-api
Query the user's local and synced-device Screenpipe data via the REST API at localhost:3030. Use for screen activity, meetings, apps, productivity, other-device or cross-device history, media export, retranscription, or connected services.
release
Release the screenpipe monorepo. Bumps versions, triggers GitHub Actions for app, CLI, MCP, and JS packages.
screenpipe-cli
Manage screenpipe pipes (scheduled AI automations) and connections (Telegram, Slack, Discord, etc.) via the CLI. Use when the user asks to create, list, enable, disable, run, or debug pipes, or manage service connections from the command line.