More screenshots
Works with the AI Agents you already use
Discord Bot Safety Check
Check Discord bots before you run or ship them: bot tokens and webhook URLs in committed files, interactions endpoints without signature checks, eval commands, @everyone pings from user text, unchecked ban commands.
$5
Discord Bot Safety Check
Example session with this skill installed
Check this project with discord-bot-safety-check.
- Read your context and instructions
- Compiled the discord bot safety
$ python3 scripts/check_discord.py examples/risky
BLOCK interactions/server.js:8 D03 INTERACTIONS_WITHOUT_SIGNATURE_CHECK
app.post('/interactions', async (req, res) => {
Why: An HTTP route or serverless handler answers Discord interactions (it checks the request for the PING) but nothing in the file or project calls a check of the X-Signature-Ed25519 and X-Signature-Timestamp headers against the app's public key; importing the helper or reading the header is not enough. Discord requires the check on every request; without it anyone who finds the URL can send forged commands and button clicks as any user. Discord also sends invalid signatures on purpose and removes an endpoint URL that accepts them.
Safer: Verify each request over the raw body and the timestamp before handling it, and answer 401 when it fails: verifyKeyMiddleware(process.env.PUBLIC_KEY) or verifyKey() from discord-interactions in Node, verify_key_decorator or PyNaCl's VerifyKey in Python.
BLOCK src/alerts.js:2 D02 WEBHOOK_URL_IN_CODE
BLOCK src/index.js:28 D04 CODE_OR_SHELL_FROM_CHAT
BLOCK src/index.js:38 D01 TOKEN_OR_SECRET_IN_CODE
REVIEW README.md:7 D15 ADMIN_INVITE
REVIEW cogs/owner.py:14 D18 OWNER_ONLY_EVAL
REVIEW src/index.js:10 D13 UNUSED_PRIVILEGED_INTENT
REVIEW src/index.js:16 D16 TOKEN_OR_SECRET_LOGGED
REVIEW src/index.js:19 D14 BOT_MESSAGES_NOT_IGNORED
REVIEW src/index.js:25 D11 MENTIONS_NOT_LIMITED
REVIEW src/index.js:33 D12 MODERATION_WITHOUT_PERMISSION_CHECK
REVIEW tools/autoreact.js:2 D17 USER_ACCOUNT_AUTOMATION
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 7 files, 7 with Discord bot content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
client.login("MTIz...") in index.js hands your bot to anyone who can read the repository, and a !say command that runs message.channel.send(args.join(" ")) lets any member make the bot ping @everyone. This skill finds those and the other Discord bot mistakes listed below before you run or ship the bot, and tells you how to fix each one.
Your agent runs a scanner on your discord.js and discord.py projects (including the py-cord, nextcord and disnake forks), HTTP interactions endpoints in Node or Python, and their .env, config, package.json, requirements and README files. It recognises Discord's token and webhook formats (and skips Discord's own documented sample token), follows text from messages, command arguments and slash-command options through assignments, knows that interaction replies and webhooks ping only users by default, and reads the whole project before judging a file: a client-level allowedMentions, a signature check in middleware, an intent used in another file. It reads your .gitignore files, so a token in a config.json or .env that git ignores is not reported as a leak, and it lists at most 50 findings per rule and file. It never runs your bot or contacts Discord. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- D01: bot tokens, user-account tokens, client secrets and other secret-named values in files git will commit, including literals passed to client.login() or bot.run()
- D02: webhook URLs with their token in files git will commit
- D03: HTTP interactions endpoints and serverless handlers that answer Discord's PING but never call an Ed25519 signature check
- D04: eval, new Function, the vm module, exec or shell commands fed with message text, command arguments or slash-command options, with no check against the bot owner's ID
REVIEW
- D11: user text sent as a regular message without allowed-mentions limits or cleaning
- D12: ban, kick, timeout, bulk delete or purge commands without a member permission check
- D13: privileged intents (Message Content, Server Members, Presence, Intents.all()) that no scanned code uses
- D14: messageCreate or on_message handlers that send messages without ignoring bots
- D15: bot invite links, generateInvite or oauth_url asking for Administrator
- D16: tokens or secrets written to console, logger, print or logging calls
- D17: self-bot libraries (discord.js-selfbot-v13, discord.py-self, selfcord, discum) or self_bot=True
- D18: eval or shell commands limited to the bot owner, and the jishaku extension
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and official documentation link for each rule
- A risky and a safe example project, and the real report the scanner produces on the risky one
Limits It reads each file as written and follows chat text through simple assignments in the same file and discord.py command parameters, not through helper functions in other files. Permission checks in custom decorators or middleware with unusual names may not be recognised. Intent use is judged from the scanned files, so scan the whole project. Command permissions changed by server admins, Developer Portal settings and the bot's real role permissions are not visible in code, and git history is not read. Libraries other than discord.js, discord.py and its forks (such as Eris, hikari, discordgo or JDA) are not checked. NOT FLAGGED is not a guarantee.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.
Static check of file text. Values passed between modules, server-side command permission overrides, Developer Portal settings and git history are not checked. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes clearly fake, inert values (not-a-real-..., EXAMPLE) for the scanner to find. Nothing in it is run.