So, as hv suggests, you're asking when does the Module do so much that the script is too minimal.
I agree with him that a script which has nothing in it but a single call to a module is fine, as is one that just has config info. However, I think your intuition that someting is odd might be coming from another source. You're putting code in the module so it they can be used in more than once. The things that are different from case to case aren't code, however, they are data. Thus the task could also be organized as a single script which selects among configuration as one of its actions. It could take the config data from a hash in the script, a singele config file with sections to choose from, or a set of distinct config files.
In that model, you put the code at the top level of attention, with the config below it. That may be clearer, or it may not, and that's one of the choices you make in deciding what "simple" means in this case and it's context.
Putting the config info conceptually below the code is an organization worth considering (and maybe rejecting), but I think that's what's tugging at the intuitions in the back of your head.