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 AndyZhuang/Opentest --skill tooluniverse-disease-researchgit clone --depth 1 https://github.com/AndyZhuang/OpentestWrote 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/andyzhuang/opentest/tooluniverse-disease-research)<a href="https://agentmods.dev/skills/andyzhuang/opentest/tooluniverse-disease-research"><img src="https://agentmods.dev/badge/skills/andyzhuang/opentest/tooluniverse-disease-research/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/andyzhuang/opentest/tooluniverse-disease-research"><img src="https://agentmods.dev/badge/skills/andyzhuang/opentest/tooluniverse-disease-research.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.00061 | $0.04814 |
| Opus 5 | $0.00030 | $0.02407 |
| Sonnet 5 | $0.00012 | $0.00963 |
| Haiku 4.5 | $0.00006 | $0.00481 |
Grade A, and why
tooluniverse-disease-research 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 9d 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 — 631 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ToolUniverse Disease Research
Generate a comprehensive, detailed disease research report with full source citations. The report is created as a markdown file and progressively updated during research.
IMPORTANT: Always use English disease names and search terms in tool calls, even if the user writes in another language. Only try original-language terms as a fallback if English returns no results. Respond in the user's language.
When to Use
Apply when the user:
- Asks about any disease, syndrome, or medical condition
- Needs comprehensive disease intelligence
- Wants a detailed research report with citations
- Asks "what do we know about [disease]?"
Core Workflow: Report-First Approach
DO NOT show the search process to the user. Instead:
- Create report file first - Initialize
{disease_name}_research_report.md - Research each dimension - Use all relevant tools
- Update report progressively - Write findings to file after each dimension
- Include citations - Every fact must reference its source tool
User: "Research Parkinson's disease"
Agent Actions (internal, not shown to user):
1. Create "parkinsons_disease_research_report.md" with template
2. Research DIM 1 → Update Identity section
3. Research DIM 2 → Update Clinical section
4. ... continue for all 10 dimensions
5. Present final report to user
Report Template
Create this file structure at the start:
# Disease Research Report: {Disease Name}
**Report Generated**: {date}
**Disease Identifiers**: (to be filled)
---
## Executive Summary
(Brief 3-5 sentence overview - fill after all research complete)
---
## 1. Disease Identity & Classification
### Ontology Identifiers
| System | ID | Source |
|--------|-----|--------|
| EFO | | |
| ICD-10 | | |
| UMLS CUI | | |
| SNOMED CT | | |
### Synonyms & Alternative Names
- (list with source)
### Disease Hierarchy
- Parent:
- Subtypes:
**Sources**: (list tools used)
---
## 2. Clinical Presentation
### Phenotypes (HPO)
| HPO ID | Phenotype | Description | Source |
|--------|-----------|-------------|--------|
### Symptoms & Signs
- (list with source)
### Diagnostic Criteria
- (from literature/MedlinePlus)
**Sources**: (list tools used)
---
## 3. Genetic & Molecular Basis
### Associated Genes
| Gene | Score | Ensembl ID | Evidence | Source |
|------|-------|------------|----------|--------|
### GWAS Associations
| SNP | P-value | Odds Ratio | Study | Source |
|-----|---------|------------|-------|--------|
### Pathogenic Variants (ClinVar)
| Variant | Clinical Significance | Condition | Source |
|---------|----------------------|-----------|--------|
**Sources**: (list tools used)
---
## 4. Treatment Landscape
### Approved Drugs
| Drug | ChEMBL ID | Mechanism | Phase | Target | Source |
|------|-----------|-----------|-------|--------|--------|
### Clinical Trials
| NCT ID | Title | Phase | Status | Intervention | Source |
|--------|-------|-------|--------|--------------|--------|
### Treatment Guidelines
- (from literature)
**Sources**: (list tools used)
---
## 5. Biological Pathways & Mechanisms
### Key Pathways
| Pathway | Reactome ID | Genes Involved | Source |
|---------|-------------|----------------|--------|
### Protein-Protein Interactions
- (tissue-specific networks)
### Expression Patterns
| Tissue | Expression Level | Source |
|--------|------------------|--------|
**Sources**: (list tools used)
---
## 6. Epidemiology & Risk Factors
### Prevalence & Incidence
- (from literature)
### Risk Factors
| Factor | Evidence | Source |
|--------|----------|--------|
### GWAS Studies
| Study | Sample Size | Findings | Source |
|-------|-------------|----------|--------|
**Sources**: (list tools used)
---
## 7. Literature & Research Activity
### Publication Trends
- Total publications (5 years):
- Current year:
- Trend:
### Key Publications
| PMID | Title | Year | Citations | Source |
|------|-------|------|-----------|--------|
### Research Institutions
- (from OpenAlex)
**Sources**: (list tools used)
---
## 8. Similar Diseases & Comorbidities
### Similar Diseases
| Disease | Similarity Score | Shared Genes | Source |
|---------|-----------------|--------------|--------|
### Comorbidities
- (from literature/clinical data)
**Sources**: (list tools used)
---
## 9. Cancer-Specific Information (if applicable)
### CIViC Variants
| Gene | Variant | Evidence Level | Clinical Significance | Source |
|------|---------|----------------|----------------------|--------|
### Molecular Profiles
- (biomarkers)
### Targeted Therapies
| Therapy | Target | Evidence | Source |
|---------|--------|----------|--------|
**Sources**: (list tools used)
---
## 10. Drug Safety & Adverse Events
### Drug Warnings
| Drug | Warning Type | Description | Source |
|------|--------------|-------------|--------|
### Clinical Trial Adverse Events
| Trial | Drug | Adverse Event | Frequency | Source |
|-------|------|---------------|-----------|--------|
### FAERS Reports
- (FDA adverse event data)
**Sources**: (list tools used)
---
## References
### Data Sources Used
| Tool | Query | Section |
|------|-------|---------|
### Database Versions
- OpenTargets: (version/date)
- ClinVar: (version/date)
- GWAS Catalog: (version/date)
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.
- 9d ago First seen · 631 lines · 61 tokens per session scan A 6bdf46b74a8c
tooluniverse-disease-research is a skill published in the GitHub repository AndyZhuang/Opentest (22 stars, last pushed 6mo ago), licensed MIT. It adds 61 tokens to every session and 4,814 once invoked, about $0.0003 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-09-03.
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…
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.
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…
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…