research-lookup

research-lookup is a skill for Claude Code from synthetic-sciences/openscience. It costs 95 tokens per session (929 once invoked), scanned A, original, Apache-2.0.

A research assistant for answering one focused factual or technical question from current sources. It reads the relevant paper, documentation, or web page rather than relying on a search-result summary.

In plain words
What is it for?
Use it to check definitions, numbers, software behavior, methods, paper findings, and current information. It helps locate the source that directly supports the answer and provide links or cited passages.
Why use it?
It helps prevent confident answers based on memory, outdated information, or a snippet taken out of context. The search is kept focused instead of becoming an unnecessarily broad review.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to check definitions, numbers, software behavior, methods, paper findings, and current information. It helps locate the source that directly supports the answer and provide links or cited passages.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/synthetic-sciences/openscience/research-lookup
About the project

synthetic-sciences/openscience is an AI workbench that carries out scientific research by reading papers, forming hypotheses, writing and running code, conducting experiments, analyzing results, and preparing reports. Researchers use it for work in machine learning, biology, physics, and chemistry with remote or local models. Catalogue add-ons extend its scientific workflows through skills and instructions.

synthetic-sciences/openscience · 4,025 stars · on GitHub · openscience.sh

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.

Any agent
npx skills add synthetic-sciences/openscience --skill research-lookup
Clone the repo
git clone --depth 1 https://github.com/synthetic-sciences/openscience

Made for: Claude Code.

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 research-lookup

README.md
[![agentmods](https://agentmods.dev/badge/skills/synthetic-sciences/openscience/research-lookup/github.svg)](https://agentmods.dev/skills/synthetic-sciences/openscience/research-lookup)
Your own site
<a href="https://agentmods.dev/skills/synthetic-sciences/openscience/research-lookup"><img src="https://agentmods.dev/badge/skills/synthetic-sciences/openscience/research-lookup/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.

agentmods 80×15 button for research-lookup

Your own site · 80×15
<a href="https://agentmods.dev/skills/synthetic-sciences/openscience/research-lookup"><img src="https://agentmods.dev/badge/skills/synthetic-sciences/openscience/research-lookup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 929 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00095 $0.00929
Opus 5.5 $0.00038 $0.00372
Sonnet 5.5 $0.00019 $0.00186
Haiku 4.5 $0.00010 $0.00093

Measured 1mo ago against content hash 609523415379, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

research-lookup 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.

backend/cli/skills/core/research-lookup/SKILL.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.

Research lookup

A lookup answers one question with the source that answers it. The failure modes are answering from memory with a confident tone, and turning a two-minute question into a survey. Both are avoided by deciding what would settle the question before searching.

Rules

  1. Decide the settling evidence first. A definition needs the defining source; a number needs the table it came from; "does library X do Y" needs the documentation or the code; "what did paper P find" needs paper P.
  2. Search where the answer lives. Scholarly claims: literature search (OpenAlex and arXiv together), then literature read with the DOI or arXiv id and a query for the passage; PubMed, Crossref and the exact API requests are in skills/core/citations/references/apis.md. Software: the project's docs or repository. Current events, prices, availability: research_search. Do not use a general web search for a scholarly claim when the paper itself is one request away.
  3. Read the source, not the snippet. Fetch the page or abstract and quote the sentence or number that answers the question, with its conditions.
  4. Two sources when the answer is contested or numeric. Agreement settles it; a disagreement is reported as one.
  5. Stop at the answer. If the question turns out to need a ranked reading of the field, say so and load literature-review instead of expanding this loop.
  6. Never present recall as lookup. If nothing was fetched, the answer says it comes from background knowledge and how confident that is.

Workflow

  1. Restate the question in one line and name the evidence that would settle it.
  2. Make one focused query per source (at most two sources); fetch the best hit.
  3. Extract the answer with its exact wording, number, units, date and conditions.
  4. Answer in one to three sentences, then the source links. Add the caveat if the source is a preprint, a blog, a vendor page, or older than the question implies.

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. 1mo ago Changed · +6 lines 609523415379
  2. 1mo ago First seen · 67 lines · 95 tokens per session scan A 25bcca382784

Subscribe to this mod's changes

research-lookup is a skill published in the GitHub repository synthetic-sciences/openscience (4,025 stars, last pushed today), licensed Apache-2.0. It adds 95 tokens to every session and 929 once invoked, about $0.0004 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-09-14.