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 system-dependency-version-checkinggit 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/system-dependency-version-checking)<a href="https://agentmods.dev/skills/holobiomicslab/asb-skill-collections/system-dependency-version-checking"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/system-dependency-version-checking/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/system-dependency-version-checking"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/system-dependency-version-checking.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.00068 | $0.02025 |
| Opus 5 | $0.00034 | $0.01012 |
| Sonnet 5 | $0.00014 | $0.00405 |
| Haiku 4.5 | $0.00007 | $0.00202 |
Grade A, and why
system-dependency-version-checking 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 6d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
system-dependency-version-checking
Summary
Detect and validate installed dependency binaries (bowtie2, samtools, R, Python) against minimum version requirements, and automatically install missing or outdated tools to ensure pipeline environment compatibility. This skill bridges the gap between user configuration and runtime readiness in bioinformatics pipelines.
When to use
You are preparing to run a complex multi-tool bioinformatics pipeline (such as HiC-Pro) on a new system or cluster, and need to confirm that all required binaries exist in the execution environment and meet minimum version thresholds (e.g., samtools >=1.9, Python >3.7) before launching data processing workflows.
When NOT to use
- You are running a containerized pipeline (Docker, Singularity) where all dependencies are already pinned and installed inside the image — the container build process, not the end-user, is responsible for version checking.
- You have a pre-built, system-wide installation of all tools that is guaranteed to be compatible (e.g., managed by a cluster admin via module systems like Lmod); direct path lookup is sufficient.
- Your pipeline is designed to use only system-provided binaries and does not support automatic installation fallback.
Inputs
- config-install.txt (template configuration file with placeholder tool paths)
- System PATH environment variable
- User-edited configuration entries for PREFIX, BOWTIE2_PATH, SAMTOOLS_PATH, R_PATH, PYTHON_PATH, CLUSTER_SYS
Outputs
- config-system.txt (locked, system-specific configuration with validated tool paths and versions)
- Installation artifacts for automatically installed tools (bowtie2, samtools binaries if required)
- Version validation report (implicit in successful config-system.txt generation)
How to apply
First, define explicit version and path requirements for each dependency (bowtie2, samtools, R, Python) in a configuration template (config-install.txt). For each dependency not explicitly set by the user, query the system PATH using the 'which' command to locate the binary. Once located, validate the installed version against the minimum threshold (samtools >=1.9, Python >3.7). If a required binary is missing or the version is below the threshold, trigger automatic installation of pre-packaged binaries (bowtie2 and samtools >=1.9 support auto-install). Compile all detected paths and system parameters into a read-only system configuration file (config-system.txt) that the pipeline will reference at runtime. This ensures that version conflicts are resolved before execution begins, and users have a locked record of which tool versions were actually used.
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.
- 6d ago First seen · 118 lines · 68 tokens per session scan A bfc0cd7dfaf8
system-dependency-version-checking is a skill published in the GitHub repository HolobiomicsLab/asb-skill-collections (15 stars, last pushed 2d ago), licensed Apache-2.0. It adds 68 tokens to every session and 2,025 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-06.
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…