In the Mac OS there is a very useful feature called the Script Menu. It allows the user to execute AppleScripts from the Menu Bar.
It appeared first in the Classic OS and was available to the right of the application’s own menus (to the left of the universally-available “Help” menu):

It was available on a per-application basis – if the foremost application did not support the menu then it would not appear. In order to populate the menu you would place AppleScripts in an application-specific folder. e.g. for iTunes a folder called “Scripts” of the iTunes folder (Which was generally in the Applications folder.) The user could also place scripts in their Documents > iTunes folder for scripts that were available for that user only.

• It was implemented as a Menu Extra – in the top right of the Menu Bar – like the Volume and Battery menu extras. I personally prefer this – it seemed out of place amongst text-based menus.
• It is not limited to AppleScripts – it can also run Shell Scripts.
• Instead of each application managing it’s own script collections in odd folders scattered all over the filesystem there was now a central repository for Menu Scripts – The “Scripts” folder of the Library.
• Because it uses the Library it respects the “cascading” metaphor that Mac OS X inherited from NeXT – The idea that Library resources are a composite of resources from the Network , Host & User libraries. This means you can have scripts available to all users on your OS X Server network, available to all users on a specific machine (host) or just available to one user – The scale of availability depends on which Library the resource is placed in.
• It uses the “Application Support” metaphor to allow scripts to be application-specific – if you are running an application called FOO the Script Menu will also show Scripts that are at the path Library/Scripts/Applications/FOO/ (remember that Library is any of the three available Libraries.)