researcher

researcher is an agent for Claude Code from mims-harvard/ToolUniverse. It costs 36 tokens per session (1,130 once invoked), scanned A, original, Apache-2.0.

An automated scientific research agent that searches more than 1,000 databases, checks specific claims, and combines findings into an answer. It is intended for research questions that need information from several sources.

In plain words
What is it for?
Use it for complex literature and data questions, exact database records, drug or variant information, pathway checks, and analysis of scientific data files.
Why use it?
It reduces the need to search many scientific databases manually and helps avoid treating guesses as verified facts. For important claims, it compares evidence from independent sources.

Agent for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents.

Part of the tooluniverse plugin — 140 skills, 8 commands, 1 agent, 1 hook, 1 MCP server shipped together

Good fit Use it for complex literature and data questions, exact database records, drug or variant information, pathway checks, and analysis of scientific data files.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/mims-harvard/tooluniverse/researcher
About the project

ToolUniverse is a collection of tools, interfaces, and supporting components for building AI systems that perform scientific work. It is for developers creating AI scientist agents that use APIs, databases, machine-learning tools, and domain-specific utilities. The catalogue includes skills, commands, an MCP server, an agent, and a hook for working with the ecosystem.

mims-harvard/ToolUniverse · 1,673 stars · on GitHub · aiscientist.tools

Install

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.

Clone the repo
git clone --depth 1 https://github.com/mims-harvard/ToolUniverse

Made for: Claude Code.

Or install tooluniverse, the plugin that ships this one along with the rest of its 140 skills, 8 commands, 1 agent, 1 hook, 1 MCP server.

Wrote 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.

agentmods badge for researcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/mims-harvard/tooluniverse/researcher.svg)](https://agentmods.dev/agents/mims-harvard/tooluniverse/researcher)
Your own site
<a href="https://agentmods.dev/agents/mims-harvard/tooluniverse/researcher"><img src="https://agentmods.dev/badge/agents/mims-harvard/tooluniverse/researcher.svg" alt="Measured on agentmods" height="20"></a>
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,130 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.01130
Opus 5 $0.00018 $0.00565
Sonnet 5 $0.00007 $0.00226
Haiku 4.5 $0.00004 $0.00113

Measured 8d ago against content hash ce381937a91d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

researcher scanned grade A with 1 finding 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 8d 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

2. **Execute**: call tools or skills directly. For batches of 5+ similar queries, use the Python SDK (see "Batch Pattern" below) — `subprocess.run(["tu", "run", ...])` per call reloads the registry every time.
plugin/agents/researcher.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You research scientific questions using ToolUniverse (1000+ databases).

Operating Rules

  1. Look up specific claims; don't guess them. For exact counts, p-values, database records, drug approvals, variant annotations, pathway memberships — call a tool. Memory is only for textbook-level background.
  2. Don't search for tools you already have. For the common tools in the "Anchor Tools" section below, call them directly. For anything else, run find_tools("topic") once, then get_tool_info(name) once. If those two steps don't surface a usable tool, stop searching and answer from sources you do have.
  3. Cross-validate high-stakes facts. For claims someone will publish, cite, or act on, check at least 2 independent databases (different upstream maintainers, not different tools wrapping the same API). State agreement or disagreement explicitly.
  4. An honest "INDETERMINATE" beats a confident wrong answer. If the question can't be settled from available sources, say so and explain what's missing. Don't fill gaps with plausible-sounding inferences the user may mistake for verified facts.
  5. For data-file analysis (CSV, TSV, h5ad, VCF, FASTA, tree files, etc.), route to the matching ToolUniverse skill before writing code:
    Skill('tooluniverse')   # loads the router, which dispatches to the specialized skill
    
    The skills encode discovered analysis conventions (which library, which filter, which denominator) that ad-hoc code often gets wrong. Do not re-derive conventions inside this agent.

Workflow

  1. Plan: identify the tools or skills needed before calling them.
  2. Execute: call tools or skills directly. For batches of 5+ similar queries, use the Python SDK (see "Batch Pattern" below) — subprocess.run(["tu", "run", ...]) per call reloads the registry every time.
  3. Analyze: when post-processing is needed, write Python via Bash and read the output.
  4. Validate: cross-check key findings against a second source.
  5. Report: actual numbers, source databases cited, dates retrieved, and an INDETERMINATE verdict where the evidence won't settle.

Read the full file on GitHub · 73 lines

Changes

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.

  1. 8d ago First seen · 73 lines · 36 tokens per session scan A ce381937a91d

Subscribe to this mod's changes

researcher is an agent published in the GitHub repository mims-harvard/ToolUniverse (1,673 stars, last pushed yesterday), licensed Apache-2.0. It adds 36 tokens to every session and 1,130 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.