database-lookup

database-lookup is a skill for Claude Code from yanjumlinnb-boop/scientific-agent-skills. It costs 82 tokens per session (8,227 once invoked), scanned B, a copy of database-lookup, MIT.

A reproducible lookup tool for 78 public databases covering areas such as biology, medicine, materials, finance, and demographics. It uses documented web interfaces to retrieve records and their supporting details.

In plain words
What is it for?
Use it to find compounds, genes, proteins, genetic variants, clinical trials, patents, economic indicators, structures, and astronomy objects.
Why use it?
It helps avoid manual searching and unclear results when you need reliable data from scientific or public databases. The lookup can be repeated and checked by another person or agent.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code; mentions Codex; built for cline.

Good fit Use it to find compounds, genes, proteins, genetic variants, clinical trials, patents, economic indicators, structures, and astronomy objects.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yanjumlinnb-boop/scientific-agent-skills/database-lookup
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 yanjumlinnb-boop/scientific-agent-skills --skill database-lookup
Clone the repo
git clone --depth 1 https://github.com/yanjumlinnb-boop/scientific-agent-skills

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/yanjumlinnb-boop/scientific-agent-skills/database-lookup/github.svg)](https://agentmods.dev/skills/yanjumlinnb-boop/scientific-agent-skills/database-lookup)
Your own site
<a href="https://agentmods.dev/skills/yanjumlinnb-boop/scientific-agent-skills/database-lookup"><img src="https://agentmods.dev/badge/skills/yanjumlinnb-boop/scientific-agent-skills/database-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 database-lookup

Your own site · 80×15
<a href="https://agentmods.dev/skills/yanjumlinnb-boop/scientific-agent-skills/database-lookup"><img src="https://agentmods.dev/badge/skills/yanjumlinnb-boop/scientific-agent-skills/database-lookup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 8,227 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00082 $0.08227
Opus 5 $0.00041 $0.04113
Sonnet 5 $0.00016 $0.01645
Haiku 4.5 $0.00008 $0.00823

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

Security

Grade B, and why

database-lookup scanned grade B with 2 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 12d 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.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

| Open Targets | GraphQL endpoint | `curl -X POST -H "Content-Type: application/json" -d '{"query":"..."}' https://api.platform.opentargets.org/api/v4/graphql` |

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

These databases require HTTP POST and **will not work with WebFetch** (GET-only). Use `curl` via your platform's shell tool instead:
Origin

This is a copy

100% identical to database-lookup — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/database-lookup/SKILL.md · 522 lines

How it starts

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

Database Lookup

You have access to 78 public databases through documented REST APIs. Your job is to turn the user's intent into a reproducible retrieval: select the authoritative database(s), make complete and rate-limited API calls, verify counts when completeness matters, and return results with enough provenance that another agent or human can repeat the lookup.

For complex biomedical retrievals, assume small filtering differences can change downstream conclusions. Prefer deterministic APIs, explicit identifiers, exhaustive pagination, and auditable logs over broad searching or plausible summaries.

Core Workflow

  1. Define the retrieval contract — Identify the target entity, accepted identifiers, organism/taxon/build/date constraints, filters, expected output fields, and whether the user needs an exhaustive dataset or a targeted lookup. If a required scientific constraint is missing and affects correctness, ask a clarifying question rather than guessing.

  2. Select authoritative database(s) — Use the database selection guide below. Prefer the primary database for the user's intent, then add cross-check databases only for identifier resolution, validation, or known coverage gaps. Do not fan out across many APIs just because they are available.

  3. Read the reference file and retrieval contract — Each database has a reference file in references/ with endpoint details, query formats, and example calls. Read the relevant file(s) and references/retrieval-contract.md before making API calls.

  4. Plan filter semantics before calling — Separate filters the API enforces server-side from filters that must be checked locally. Note identifier conversions, fields with ambiguous meanings, pagination strategy, rate limits, and any data-source conventions such as RefSeq vs GenBank or genome build.

  5. Make complete API calls — See the Making API Calls section below. For exhaustive retrievals, count first when the API supports it, paginate or batch until retrieved counts reconcile, and fail visibly if the final dataset is incomplete.

Read the full file on GitHub · 522 lines

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 12d ago First seen · 522 lines · 82 tokens per session scan B eec04f1c4c12

Subscribe to this mod's changes

database-lookup is a skill published in the GitHub repository yanjumlinnb-boop/scientific-agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 82 tokens to every session and 8,227 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). It is 100% identical to database-lookup, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

instrument-data-to-allotrope

Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…

anthropics/knowledge-work-plugins · 123 tokens

matlab

Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.

K-Dense-AI/scientific-agent-skills · 42 tokens

exploratory-data-analysis

Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…

K-Dense-AI/scientific-agent-skills · 83 tokens

phylogenetics

Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.

K-Dense-AI/scientific-agent-skills · 68 tokens

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

mapping-to-snomed

Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…

maziyarpanahi/openmed · 205 tokens