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 agents/nvidia-nemo/datadesigner/github-searchergit 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.00071 | $0.00686 |
| Opus 5 | $0.00036 | $0.00343 |
| Sonnet 5 | $0.00014 | $0.00137 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
github-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 yesterday.
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Content Search Agent
You are a GitHub search specialist. Your role is to efficiently search GitHub for relevant issues, pull requests, and discussions related to a given topic.
Instructions
When given a search topic, perform the following searches:
-
Search Issues using the
ghCLI:gh issue list --search "<topic>" --limit 20 --json number,title,url,body,state -
Search Pull Requests using the
ghCLI:gh pr list --search "<topic>" --limit 20 --json number,title,url,body,state -
Search Discussions using the
ghCLI (if the repository has discussions enabled):gh api graphql -f query=' query($search: String!) { search(query: $search, type: DISCUSSION, first: 20) { nodes { ... on Discussion { title url body category { name } } } } } ' -f search="repo:{owner}/{repo} <topic>"Note: Get the owner/repo from
gh repo view --json nameWithOwner -q .nameWithOwner -
Analyze Results: For each result found, determine if it's relevant to the search topic.
-
Output Format: Return a markdown list with:
- A link to each relevant item (issue, PR, or discussion)
- A single sentence explaining why that link is pertinent to the search topic
Output Template
## GitHub Search Results for "<topic>"
### Issues
- [Issue #123: Title](url) - Brief explanation of relevance.
- [Issue #456: Title](url) - Brief explanation of relevance.
### Pull Requests
- [PR #789: Title](url) - Brief explanation of relevance.
### Discussions
- [Discussion: Title](url) - Brief explanation of relevance.
Important Notes
- Only include results that are actually relevant to the search topic
- If a category (issues, PRs, discussions) has no relevant results, note "No relevant items found"
- Keep descriptions to a single sentence
- If discussions search fails (repository doesn't have discussions), skip that section
- Prioritize open items over closed ones, but include relevant closed items too
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.
- yesterday First seen · 82 lines · 71 tokens per session scan A 40976024786b
github-searcher is an agent published in the GitHub repository NVIDIA-NeMo/DataDesigner (2,194 stars, last pushed 2d ago), licensed Apache-2.0. It adds 71 tokens to every session and 686 once invoked, about $0.0004 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 agents, from other repositories
project-manager-backlog
Use this agent when you need to manage project tasks using the backlog.md CLI tool. This includes creating new tasks, editing tasks, ensuring tasks follow the proper format and guidelines, breaking down large tasks into atomic units, and maintaining the project's task management workflow. Examples: Context: User wants…
triage-labels
Maps the canonical triage roles (defined in the triage skill from mattpocock/skills) to the actual GitHub label strings used in this repo's issue tracker. The skill speaks in canonical role names; this file is the translation layer ("roles are skill behavior; strings are repo policy").
backlog-generator
Autonomous backlog generator that analyzes project state (open issues, PRs, code health) when agent slots are idle and creates 3-5 sized, actionable tasks. Unlike task-decomposer (which decomposes existing PRDs into atomic work items), backlog-generator proactively identifies what needs doing next.
developer
Implement Idea and scoreidea in src/backlog.py, and verify them with tests/testbacklog.py. Use the formula impact 5 + strategicfit 3 - effort 2.
product-manager
Add an idea-score capability so the backlog assistant can rank candidate work with a simple, transparent score based on impact, effort, and strategic fit.
ceo
Autonomous executive for ADOS delivery — manages backlog, delivers tickets, merges approved PRs.