Well I finally got around to making myself a few simple scripts last night, might as well share I suppose, do with them what you like.
I might add some disclaimers and prompts if I feel like it later.
I assume they aren't appropriate for boot scripts, were only intended for my own casual use anyway, and in fact I'm not even sure what if anything extra is involved with implementing scripts as boot scripts.

You can find them here:
ocScripts-0.01.zip

ocScripts-0.02.zip - what can I say, I got bored.

You can either have your opptimizer_n9.ko and symsearch.ko located in /home/user/MyDocs/Documents/ocmodules-pr1.2/ like mine, or you can edit install.sh to match your own directory structure, this only affects install.sh at this stage anyway.

A description of the individual scripts as follows:
installOC.sh - will copy symsearch.ko and opptimizer.ko to modules directory, ready to be loaded.
uninstallOC.sh - will delete symsearch.ko and opptimizer.ko from modules directory.
activateOC.sh - will load modules via insmod.
resetOC.sh - this was supposed to return frequency and smart reflex to defaults, note that at the time of writing this, the script is pretty much useless and will cause a reboot, it might work down the track, hence why I left it included, but you might prefer to delete this one for now. (removed in ocScripts0.02)

next four are self explanatory....
setFreq1.1ghzSRoff.sh - set frequency to 1.1ghz and disable smart reflex.
setFreq1.1ghzSRon.sh - set frequency to 1.1ghz and enable smart reflex.
setFreq1.1ghzSRoff.sh - set frequency to 1.2ghz and disable smart reflex.
setFreq1.2ghzSRon.sh - set frequency to 1.2ghz and enable smart reflex. (ocScripts 0.02 only)

To run a script via the terminal, simply cd to the directory where the script is located, and run a command like: sh installOC.sh

The correct order to run these scripts if the modules aren't installed would be like this example:
or to just re-enable the overclock after a reboot you would do it like this:
Extra notes of caution:
These scripts obviously use opensh, which itsnotabigtruck correctly opposes, use them at your own peril, anyone with a sense of caution should check for themselves to know there's nothing malicious in them, they're a temporary solution at best but they seem to work for now at least.
I recommend against running a second setFreq script without a reboot as it'll probably result in a reboot itself, just like reset.sh.
These scripts come with a warranty ONLY in HanzBlixLand, for you the warranties simply not valid, sorry.
And finally, any time that Creamy Goodness updates his modules, these scripts are liable to be broken, don't complain, he needs the freedom to adjust the modules however he deems appropriate.