Antinuke
Antinuke limits how many sensitive actions a moderator can take in a short window. If they exceed the threshold, Skill applies a punishment and can alert you.
Overview
Why use it?
Stops compromised or abusive staff from mass banning, kicking, deleting channels/roles, or spamming webhooks before you can react.
How it works
Each module (ban, kick, channel, role, emoji, webhook, …) has its own threshold and punishment. The master switch must be on, and each module you care about must be enabled separately.
Master switch
;antinuke enable — turn the system on;antinuke disable — turn it off;antinuke or ;antinuke config — view full config
Who can configure it
Initially only the server owner (and bot owner). Grant others with:
;antinuke admin @user — toggle antinuke admin (powerful);antinuke admins — list antinuke admins
Antinuke admins can also open this server in the dashboard. Granting admin is owner-only so a compromised admin cannot recruit more.
Whitelist
;antinuke whitelist @user — exempt a user or bot from checks
Whitelisted accounts bypass antinuke entirely. Use sparingly.
Modules
Each protects against a burst of that action from one actor. Recommended thresholds are low (about 1–6). Use --do for the punishment and --threshold for the limit. Include --command on if bot ban/kick commands should count.
;antinuke ban on --threshold 3 --do ban --command on;antinuke kick on --threshold 3 --do stripstaff;antinuke channel on --threshold 2 --do ban;antinuke role on --threshold 2;antinuke webhook on --threshold 2;antinuke emoji on --threshold 3;antinuke botadd on — remove unauthorized bots on join;antinuke vanity on --do ban — vanity URL changes
Turn a module off with the same command and off.
Staff role & permissions watch
;antinuke staffrole @Role — role removed by stripstaff punishment;antinuke permissions — watch dangerous Discord permissions with their own punishments
View status
;antinuke config · ;antinuke list · ;antinuke admins
Full command list: Antinuke commands.