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 skills add Sage-Bionetworks/agent-skills --skill scientific-metadata-extractiongit clone --depth 1 https://github.com/Sage-Bionetworks/agent-skillsWrote 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/skills/sage-bionetworks/agent-skills/scientific-metadata-extraction)<a href="https://agentmods.dev/skills/sage-bionetworks/agent-skills/scientific-metadata-extraction"><img src="https://agentmods.dev/badge/skills/sage-bionetworks/agent-skills/scientific-metadata-extraction/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.
<a href="https://agentmods.dev/skills/sage-bionetworks/agent-skills/scientific-metadata-extraction"><img src="https://agentmods.dev/badge/skills/sage-bionetworks/agent-skills/scientific-metadata-extraction.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.02531 |
| Opus 5 | $0.00000 | $0.01265 |
| Sonnet 5 | $0.00000 | $0.00506 |
| Haiku 4.5 | $0.00000 | $0.00253 |
Grade A, and why
scientific-metadata-extraction 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 11d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scientific Metadata Extraction
Overview
Patterns for extracting and normalizing metadata from scientific data repositories (GEO, SRA/ENA, PRIDE, BioStudies, PubMed) and publication sources. Covers per-sample identifier derivation, author name normalization, assay type determination, species verification, file format normalization, and a 4-tier gap-fill strategy for resolving missing annotation fields.
Installation
pip install biopython httpx
Authentication
from Bio import Entrez
import os
Entrez.email = "[email protected]"
if os.environ.get("NCBI_API_KEY"):
Entrez.api_key = os.environ["NCBI_API_KEY"] # raises limit from 3 to 10 req/s
Core Concepts
- Per-sample metadata: Annotation fields that describe biological properties (tissue, genotype, sex, condition) vary between samples and must be fetched from per-sample records — never copied from a single study-level value.
- Repository submitter ≠ PI: Repository submitter fields reflect whoever deposited the files, often a postdoc or research engineer. Investigator/PI fields should come from the PubMed AuthorList.
- Run accession ≠ biological ID: SRR/ERR/DRR accessions identify sequencing runs, not specimens. Use BioSample IDs or sample titles as specimen identifiers.
- Assay type from library metadata: Publication titles describe biology, not technology. Always verify assay type from
library_strategy/library_sourcein repository records.
Common Operations
Fetch Study Leads from PubMed
Always derive investigator names from the PubMed AuthorList — first author + last/corresponding author in "Firstname Lastname" format.
from Bio import Entrez
def fetch_study_leads(pmid: str) -> list[str]:
"""Return [first_author, last_author] as 'Firstname Lastname' strings."""
handle = Entrez.efetch(db="pubmed", id=str(pmid), rettype="xml", retmode="xml")
recs = Entrez.read(handle)
authors = recs["PubmedArticle"][0]["MedlineCitation"]["Article"]["AuthorList"]
def fmt(auth) -> str:
fore = str(auth.get("ForeName", ""))
last = str(auth.get("LastName", ""))
return f"{fore} {last}".strip()
leads = [fmt(authors[0]), fmt(authors[-1])]
return list(dict.fromkeys(leads)) # deduplicate if single-author paper
# Reformat GEO-style "Lastname FI" contributors
import re
def normalize_author_name(name: str) -> str:
"""'Smith JP' → 'J Smith', 'Doe, Jane' → 'Jane Doe'"""
if "," in name:
parts = [p.strip() for p in name.split(",", 1)]
return f"{parts[1]} {parts[0]}"
tokens = name.split()
if len(tokens) == 2 and len(tokens[1]) <= 3 and tokens[1].isupper():
return f"{tokens[1][0]} {tokens[0]}"
return name
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.
- 11d ago First seen · 240 lines · 0 tokens per session scan A ec8330881a2c
scientific-metadata-extraction is a skill published in the GitHub repository Sage-Bionetworks/agent-skills (5 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,531 tokens. 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-31.
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…
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…
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.
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.
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.
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…