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 HolobiomicsLab/asb-skill-collections --skill bioinformatics-tool-version-compatibility-assessmentgit clone --depth 1 https://github.com/HolobiomicsLab/asb-skill-collectionsWrote 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/holobiomicslab/asb-skill-collections/bioinformatics-tool-version-compatibility-assessment)<a href="https://agentmods.dev/skills/holobiomicslab/asb-skill-collections/bioinformatics-tool-version-compatibility-assessment"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/bioinformatics-tool-version-compatibility-assessment/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/holobiomicslab/asb-skill-collections/bioinformatics-tool-version-compatibility-assessment"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/bioinformatics-tool-version-compatibility-assessment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00039 | $0.01842 |
| Opus 5 | $0.00019 | $0.00921 |
| Sonnet 5 | $0.00008 | $0.00368 |
| Haiku 4.5 | $0.00004 | $0.00184 |
Grade A, and why
bioinformatics-tool-version-compatibility-assessment 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 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.
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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bioinformatics-tool-version-compatibility-assessment
Summary
Assess and resolve version compatibility requirements for interdependent bioinformatics tools before pipeline execution. This skill ensures that declared tool versions (e.g., samtools ≥1.9, Python >3.7) are available in the system environment or can be automatically installed, preventing runtime failures downstream.
When to use
Before executing a complex bioinformatics pipeline (such as Hi-C data processing) that depends on multiple third-party tools with explicit version constraints. Apply this skill when tool versions are documented in configuration files or installation instructions and you need to validate that the current system environment satisfies all declared requirements, or when automatic dependency resolution is available and you must configure which tools to auto-install vs. source from PATH.
When NOT to use
- Pipeline tools are already fully installed and validated in a frozen container (Docker, Singularity) — version compatibility is pre-resolved at container build time, not at runtime.
- You are running a single-tool analysis (e.g., only bowtie2 alignment) that does not require inter-tool version coordination.
- Pipeline provides no version constraints or auto-installation mechanism — manual dependency management is required instead.
Inputs
- config-install.txt (template configuration file with tool path declarations and version requirements)
- system PATH environment variable
- installed tool binaries (samtools, bowtie2, Python, R, etc.)
- optional: full paths to pre-installed tool binaries
Outputs
- config-system.txt (resolved configuration file recording detected tool paths and versions)
- validation report indicating which tools met version thresholds
- installation log showing auto-installed dependencies (if applicable)
How to apply
First, identify all declared tool dependencies and their version thresholds from the pipeline's documentation and configuration templates (e.g., config-install.txt). Create or edit a configuration file (such as config-install.txt) to specify either full paths to tool binaries or leave version fields unset to allow automatic detection via the system PATH using the 'which' command. Then execute the pipeline's dependency-checking build target (e.g., 'make CONFIG_SYS=config-install.txt install') which validates tool availability against declared version constraints and generates a resolved configuration file (e.g., config-system.txt) recording the paths and versions of tools actually found. Finally, inspect the generated system configuration file to confirm that all tools at minimum required versions were detected and recorded, indicating readiness for pipeline stages that depend on those tools.
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.
- 12d ago First seen · 109 lines · 39 tokens per session scan A bf1cea9b0dae
bioinformatics-tool-version-compatibility-assessment is a skill published in the GitHub repository HolobiomicsLab/asb-skill-collections (15 stars, last pushed yesterday), licensed Apache-2.0. It adds 39 tokens to every session and 1,842 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
external-model-validation
Use when validating an existing prognostic risk signature on an external bulk expression cohort with survival outcomes, producing risk scores, Kaplan-Meier curves, risk distribution plots, heatmap, and time-dependent ROC curves. NOT for: model training, feature selection, nomogram construction, calibration analysis…
medical-research-literature-reader-pro
A medical-research-native literature reading skill for users with clinical, bioinformatics, translational, and basic experimental backgrounds. Use this skill whenever a user wants to read, analyze, critique, or interpret a medical or scientific paper — whether they provide a PDF, abstract, DOI, PMID, or just a title.…
adverse-event-narrative
Generates CIOMS I-compliant ICSR narratives from adverse event case data for FDA and EMA regulatory submission. Includes temporal analysis, MedDRA coding, causality assessment using WHO-UMC or Naranjo criteria, and multi-format output.
anatomy-quiz-master
Generate interactive anatomy quizzes for medical education with multiple.
decision-curve-analysis
Use when evaluating the clinical utility of a binary prediction model from a single clinical CSV file by fitting a logistic decision-curve model, plotting decision and clinical-impact curves, and exporting summary outputs. NOT for: survival calibration, ROC-only discrimination analysis, nomogram construction, or…
elastic-net-feature-selection
Use when selecting predictive genes or other molecular features from bulk expression matrices for binary case-vs-control classification with elastic net logistic regression, including coefficient path and cross-validation plots. Trigger keywords: elastic net, glmnet, feature selection, binary classification…