put your code into a ae template that reflects the way you do it OR change the entire AE Windows script.
You wont get a event out of this. So no scriptjob. Maya is not event based in this way so its not productive to extensively thinking in event driven way. So scriptjobs are VERY limited in scope. If you ever find that you run more than say 5-10 custom scriptjobs inside your maya session your not thinking things the right way most likely.
you can overload the attributeEditorVisibilityStateChange function. BUT ONLY do thsi if your tool is TOTALY separate from the AE templates and doesn't touch them in any way.* If you do you should actually do ae template modification. in form of editorTemplate -callCustom thisway you will slow down the ae template as little as possible.
PS: unless you have actually ever made a AE tempklate and a editorTemplate -call custom thing. You should learn to do so first. As the call custom does hook up events for your own ae customizations. And you can allways inject them into ae template codes dynamically.
*Maya is callback based