Controllers developed by end user

[eluser]mscahill[/eluser]
I have a conceptual question. I'm developing a reporting application where the end [power] user will develop their own controllers (in a subfolder) that will extend the functionality that the application provides. Usually I would call these modules, but I don't want to mix terminology with the MVC architecture. What can I call these controller extensions of the codebase?

For example, an end user could write a controller to interface with a document management system.

Whatever name I finally agree on would be the name of the folder within the controller folder, as well as the table in which metadata regarding the controller would be held. Any ideas?