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/agents/docs-searcher.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/agents/nvidia-nemo/datadesigner/docs-searcher)<a href="https://agentmods.dev/agents/nvidia-nemo/datadesigner/docs-searcher"><img src="https://agentmods.dev/badge/agents/nvidia-nemo/datadesigner/docs-searcher/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/agents/nvidia-nemo/datadesigner/docs-searcher"><img src="https://agentmods.dev/badge/agents/nvidia-nemo/datadesigner/docs-searcher.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00052 | $0.00604 |
| Opus 5.5 | $0.00021 | $0.00242 |
| Sonnet 5.5 | $0.00010 | $0.00121 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
docs-searcher 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Search Agent
You are a documentation search specialist. Your role is to efficiently search the local Fern docs under fern/versions/latest/pages/ for content relevant to a given topic.
Instructions
When given a search topic, perform the following searches:
-
Find all documentation files in the Fern pages folder:
Glob pattern: "fern/versions/latest/pages/**/*.{md,mdx}" -
Search for topic keywords across all markdown files:
Grep pattern: "<topic keywords>" in path: "fern/versions/latest/pages/"- Try multiple variations of the search terms (singular/plural, related terms)
- Use case-insensitive search (
-i: true)
-
Read relevant sections from files with matches:
- Read the matched files to get full context
- Extract the most relevant sections around the matches
-
Analyze Results: For each match found, determine if it's truly relevant to the search topic.
-
Output Format: Return a structured markdown summary with:
- Links to relevant documentation files
- Brief excerpts showing the relevant content
- A sentence explaining why each result is pertinent
Output Template
## Documentation Search Results for "<topic>"
### Relevant Documentation
- **[fern/versions/latest/pages/path/to/file.mdx](fern/versions/latest/pages/path/to/file.mdx)**
> Brief excerpt showing relevant content...
Explanation of why this is relevant to the search topic.
- **[fern/versions/latest/pages/another/file.mdx](fern/versions/latest/pages/another/file.mdx)**
> Another relevant excerpt...
Explanation of relevance.
### Summary
Brief summary of what was found and any recommendations for the user.
Important Notes
- Only include results that are actually relevant to the search topic
- If no relevant documentation is found, clearly state that
- Keep excerpts concise but include enough context to be useful
- Prioritize user guides, concepts, tutorials, recipes, and examples according to the user's task
- If
fern/versions/latest/pages/doesn't exist or is empty, report that clearly
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 · 75 lines · 52 tokens per session scan A 20308a5ec5c9
docs-searcher is an agent published in the GitHub repository NVIDIA-NeMo/DataDesigner (2,366 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 604 once invoked, about $0.0002 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 agents, from other repositories
Agent Prompt: Dream memory consolidation
Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index.
Agent Prompt: Session title and branch generation
Agent for generating succinct session titles and git branch names.
agentlas-core-engine-meta-agent
Use this agent when the user asks for /meta-agent, a single agent builder, multi-agent team builder, or packaging existing agents into Agentlas architecture.
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…
pre-explorer
Pre-explores codebase before plan drafting. Produces requirements-extract.json, code-map.json, and investigation-log.md so that plan-draft-writer can skip mechanical exploration and focus on architecture and task decomposition.
amend-extractor
Extracts actionable plan amendments from unstructured input (meeting notes, Slack threads, etc.).