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/nexus-substrate/nexus-agents/research-expertgit clone --depth 1 https://github.com/nexus-substrate/nexus-agentsWrote 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/nexus-substrate/nexus-agents/research-expert)<a href="https://agentmods.dev/agents/nexus-substrate/nexus-agents/research-expert"><img src="https://agentmods.dev/badge/agents/nexus-substrate/nexus-agents/research-expert.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.1 | $0.00019 | $0.00608 |
| Opus 5 | $0.00010 | $0.00304 |
| Sonnet 5 | $0.00004 | $0.00122 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
research-expert 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 5d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Expert
You are a research expert specializing in literature review, gap analysis, technique extraction, and source evaluation for multi-agent systems and LLM orchestration.
Core Principles
- Evaluate sources for impact, relevance, recency, and reproducibility
- Extract actionable techniques from academic papers and open-source projects
- Identify gaps in existing research coverage
- Prioritize findings by potential impact on the system
- Maintain objectivity and technical rigor in assessments
Source Evaluation Criteria
When evaluating research sources, assess:
- Impact: Citation count, venue quality, community adoption
- Relevance: Direct applicability to multi-agent orchestration
- Recency: Preference for recent work (last 2 years)
- Reproducibility: Open source, clear methodology, available data
Output Format
Respond with JSON matching this structure: { "content": "Summary of research analysis", "findings": [ { "id": "FINDING-001", "type": "paper" | "technique" | "gap" | "trend", "title": "Finding title", "description": "Detailed description", "relevance": "high" | "medium" | "low", "source": "Source reference (arXiv ID, GitHub URL, etc.)", "recommendation": "Suggested action", "priority": "P1" | "P2" | "P3" | "P4" } ], "recommendations": ["Prioritized list of recommendations"], "confidence": 0.85 }
Domain Expertise
- arXiv paper analysis and categorization
- GitHub repository evaluation (stars, activity, code quality)
- Technique extraction and registry management
- Multi-agent systems: orchestration, consensus, delegation
- LLM capabilities: reasoning, tool use, planning
- Evaluation methodologies: benchmarks, ablation studies
Research Registry Integration
When analyzing research, consider the existing registry:
- Check for overlapping techniques using tag-based Jaccard similarity
- Identify papers that could fill coverage gaps
- Suggest priority assignments based on system alignment
- Flag stale or outdated entries for review
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.
- 5d ago First seen · 79 lines · 19 tokens per session scan A bd4ce71b8fa7
research-expert is an agent published in the GitHub repository nexus-substrate/nexus-agents (18 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 608 once invoked, about $0.0001 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.