Be careful about using Module::Pluggable. Each time you run your script Module::Pluggable has to search through the entire INC path, and as part of that searching it will load every matching module. So, you get a win in that you can abstract out parts of your code or use separate distributions. But you also get a heavy penalty in that you might be loading large chunks of code unrelated to your current task at hand.
in reply to What is present best practices for lightweight plugins?
If you don't care to allow for arbitrary extension by third parties, then I'd use something like autouse or AutoRole to mix in known functionality.
If you want third party extensions but without the bloat, then a mapping of method name to module name is a way to go.
Alternately you could use a hybrid approach and scan @INC for module names - but don't load them unless a method that maps to a module is called.
However, with all that said, Module::Pluggable might be doing exactly what you want. I haven't had any of my personal projects ever fall into that category.
my @a=qw(random brilliant braindead); print $a[rand(@a)];