That's not a good idea, because of the multi-word commands based on a single word. Let's consider the Gallery plugin: it has a "/gallery claim" command and "/gallery reset" command. The first one should be available to all players, the second one should be available only to admins. So there's just no way to have "one command sets permissions for all commands"
When you write a plugin, you should structure your permissions properly (Gallery is a poor example, unfortunately). Make a guess at what the groups for individual commands are, and make use of permission subgroups:
"plugin.user.something1"
"plugin.user.something2"
"plugin.admin.dangerous1"
"plugin.admin.dangerous2"
This way admins can add "plugin.user.*" permission to their user rank and be done with it.
Of course, MCS supports "antipermissions", too. You can add the permission "gallery.*" and then specify restrictions as "gallery.admin.*".
I'd say these are powerful enough for most cases.
When you write a plugin, you should structure your permissions properly (Gallery is a poor example, unfortunately). Make a guess at what the groups for individual commands are, and make use of permission subgroups:
"plugin.user.something1"
"plugin.user.something2"
"plugin.admin.dangerous1"
"plugin.admin.dangerous2"
This way admins can add "plugin.user.*" permission to their user rank and be done with it.
Of course, MCS supports "antipermissions", too. You can add the permission "gallery.*" and then specify restrictions as "gallery.admin.*".
I'd say these are powerful enough for most cases.