check out discussion here :
https://www.rosettacommons.org/content/inputscorefilter-not-taken-program-cluster
and based on my experience, in 3.5 it is still not integrated.
Let me confuse you more:
In the documentation of 3.5 it is still listed as -input_score_filter
https://www.rosettacommons.org/docs/latest/cluster.html
If you read the help of cluster command: cluster –help, you will not find the option anymore. There is instead one option called -output_score_filter.
If you read the first ca. 50 lines in the output of cluster command, you find neither of such filters listed as possible options. Nevertheless, you can specify them and the program will not complain about unrecognized parameter. Just they are silently ignored in the execution.
Simply put , this score filter option does NOT work. It is not about the energy being higher/lower , beyond/below, better/worse, or whatsoever. It just does not work.