Are you familiar with repackaging Mac installers?
The installer from prey has a custom app that runs setup so it can't be used for silent installs.
You'll need to install on a test mac whist tracking file system changes. Apples Package maker will do this via it's snapshot feature (in Developer tools).
Then you'll need to put a device ID & API key into the config, a post install script can create the cron job for Prey (the Prey readme has a one liner command for this).
I assume you can run custom shell commands via Aabsolute manage eg
#!/bin/sh
curl -O my-custom-package.pkg
sudo installer my-custom-package.pkg -target /
The config will need a valid control panel device & API id - I guess it could be a list hosted on a remote server so the package is portable.
I haven't deployed Prey to 'non OS X' *nix, but maybe an apt-get (or similar) can grab & all the dependancies, but I think Prey setup will open on install, so please test :^)
Does that make sense?
Drew