Skip to main content
11 slash commands and 3 context-menu commands, sourced directly from the bot’s command registry (apps/bot/src/commands). This page is maintained by hand, not generated — if a command here looks out of date, the source is the final authority.
Permission is the AEGIS RBAC permission checked when the command actually runs — see Installation & Permissions for what each key grants. Discord-side role settings only control whether you can see a command, not whether AEGIS will let you run it. “None” means AEGIS doesn’t gate the command at all (though it may still require a Discord permission to appear, or only make sense for the person who triggered it).

​
Moderation actions

All /moderation subcommands require cases.create, and every action creates a case (see Moderation).
Permission: cases.createExample: /moderation warn member:@SomeUser reason:Repeated spam in #general
Permission: cases.createExample: /moderation note member:@SomeUser content:Flagged by another server's staff
Permission: cases.createExample: /moderation timeout member:@SomeUser duration:1h reason:Spamming in general
Permission: cases.createExample: /moderation untimeout member:@SomeUser reason:Timeout served, appeal accepted
Permission: cases.createExample: /moderation kick member:@SomeUser reason:Repeated rule violations
Supplying duration makes it a tempban instead of a permanent ban.Permission: cases.createExample: /moderation ban user:@SomeUser reason:Ban evasion duration:7d
Permission: cases.createExample: /moderation softban user:@SomeUser reason:Clearing spam messages
Permission: cases.createExample: /moderation unban user_id:123456789012345678 reason:Appeal approved
Permission: cases.createExample: /moderation quarantine member:@SomeUser reason:Suspicious activity duration:24h
Permission: cases.createExample: /moderation unquarantine member:@SomeUser reason:Cleared after review
Permission: cases.createExample: /moderation purge count:50 reason:Clearing spam raid
0 disables slowmode.Permission: cases.createExample: /moderation slowmode seconds:30 reason:High traffic during event
Permission: cases.createExample: /moderation lock reason:Active raid, locking down
Permission: cases.createExample: /moderation unlock reason:Raid contained

​
Case management

Permission: cases.readExample: /case view number:42
Permission: cases.readExample: /case list member:@SomeUser
Permission: cases.readExample: /case note number:42 content:Escalated to senior mod for review
Also subject to separation of duties — the moderator who took the original action cannot reverse it alone.Permission: cases.reverseExample: /case reverse number:42 reason:Appeal approved by second moderator

​
Security & incident response

Permission: incidents.read
level is one of: observe, heightened_verification, quarantine_new_members, restricted_messaging, emergency_lockdown.Permission: lockdown.activate (or lockdown.release when setting level back to observe)Example: /security containment set level:quarantine_new_members reason:Suspected raid in progress
type is one of: raid, anti_nuke, compromised_staff, spam_campaign, phishing_campaign, coordinated_abuse, custom. severity is one of: low, medium, high, critical. room defaults to true and creates a private incident channel.Permission: incidents.manageExample: /incident open type:raid title:Coordinated join spike severity:high
Permission: incidents.read
to is one of: investigating, contained, monitoring, resolved, closed, reopened.Permission: incidents.manageExample: /incident status number:7 to:contained note:Quarantine applied to all joiners

​
Member intelligence

Permission: members.investigateExample: /member investigate member:@SomeUser
Permission: members.investigateExample: /member trust member:@SomeUser trusted:true
Permission: members.investigateExample: /member watchlist member:@SomeUser watchlisted:true

​
Context menu commands

Right-click a member or message → Apps to reach these.
User context menu command.Permission: members.investigate
User context menu command. Opens the same confirmation panel as /moderation quarantine, pre-filled for a 24-hour quarantine.Permission: cases.create
Message context menu command. Stores a short content preview as evidence for the report (see Privacy for how that evidence is retained).Permission: None — any member who can see the message can report it.

​
Platform & setup

Permission: None
Permission: None
Permission: config.read
protection is one of: sentinel, raid, antiNuke, messageProtection, linkProtection. mode is one of: off, dry_run, log_only, human_approval, automatic.Permission: config.publishExample: /config mode protection:raid mode:human_approval
purpose is one of: log (moderation log), alert (security alerts).Permission: config.publishExample: /config set-channel channel:#mod-log purpose:log
Refuses roles that carry Administrator or Manage Server.Permission: config.publishExample: /config quarantine role:@Quarantined
app_role is one of: security_admin, incident_commander, senior_moderator, moderator, investigator, appeals_reviewer, auditor, read_only.Permission: config.publishExample: /config roles role:@Moderator app_role:moderator
Permission: config.publishExample: /config rollback version:3
Permission: config.read
hours defaults to 24.Permission: audit.readExample: /audit search action:config.publish hours:72
Permission: audit.read
Permission: None
Permission: None
Only works for a case opened against you, and is subject to a per-guild cooldown between appeals.Permission: None (self-service)Example: /appeal submit case_number:42 statement:I was not the one posting those links
Permission: None (self-service)