For WCS I'd have admins use some non-existant command to "login" & then use the bot to both set their access (or forcelogin) & report the change of status, assuming you used the command /admin rather than /login a bot response along these lines should do the trick:
<OnOpMessage type="script">
<in>/admin password</in>
<out>/setaccess %NAME% aA... sanscrit....zZ</out>
<out>%NAME% now has admin in the chanel</out>
</OnOpMessage>
this has the DISadvantage that if your admins have watchcommands.. they can see the other admin's logins, & is therefore not perfect, & would be more secure if restricted to a usergroup in the bot.. ofc your admins would then need to be consistant with their names. Possibly you could have the bot setting access as a response to /message or in <OnPM> (pm the password to bot, it responds by giving admin & reporting the fact) although pm isn't the most reliable way to trigger a bot, they have a habit of not sending & robo kinda sucks for them arriving
Obviously you'd use your own substitution for /login your own choice of password.. & set the access accordinfg to what powers each admin needs.. personally i use ouka, which reports logins to admins by default, & i simply have the bot repeat the report for the rest of the channel.