Well as far as events goes you've got
on rawmode, which is admittedly a bit awkward to parse, but there's a bit of code
here you can use to simplify accessing those mode changes.
I don't think there should be specific events for those modes because they're non-standard and could easily have different meanings on other IRCds. Better access to modes in
on rawmode events (which I've suggested previously) and a generic internal list identifier like I mentioned above should provide everything we need.
