It should be done at the startup right ?
maya loads nothing on start up unless you specifically tell it to in user setup.mel/py or some of the other bootstrap files (but if it is then i can not help you, because then its your mess and you need to sort it out, theres no single person on the planet that can help you do it here). Maya only indexes all mel file names as possibly being callable names.
Do you know where could it come from ?
most likely the scripts are just in the wrong folder. run:
getenv MAYA_SCRIPT_PATH
and see that maya is one of the ; or : delimited string as a path (yes it needs to be a FULL path and no sub folder works), note it does not mean anything that they say in the manual folder is yada yada only this list counts.
The second reason, which is more likely the culprit in this case, is that the script is missing a in-point. Scripts that you expect to be able to launch MUST have the same file name as as the global procedure within with a mel ending, anything else and maya will not find it. You can have secondary functions in one file but no other person can call these if the file name does NOT match.
in a way maya has no mechanism for loading personal procedures, just scripts that have individual files and even then only global procs in them.