Oh, I don't know about that. The frustration in failing to remember to update my call to run_modes whenever I add a new run mode function is probably worth those extra few letters on each and every function name. It can save me minutes of debugging time, which is way less effort than typing three extra characters.

Further, by the principle of keeping scope as minimal as possible, everything to do with a given run mode can be kept to just that function - I don't need to remember to go to the top (or bottom) of my module to add it to another data structure elsewhere. Having to set up run modes has to be my biggest issue with using C::A. Not that I have a better solution, mind you. It just is.

It looks to me like you traded one bit of repetitive typing (adding your mode to the run_modes list) for another (adding rm_ to the start of every runmode).

That actually doesn't bug me, since I was already naming my runmode methods rm_whatever in order to differentiate them from non-runmode methods.