This repository contains Toxic-MD, a WhatsApp multi-device bot built on Node.js using the Baileys library (reverse-engineered WhatsApp Web API). It is a plugin-based application that handles incoming WhatsApp messages, processes commands from over 200 plugins organized by category (General, Groups, Owner, AI, Downloads, Editing, Settings, etc.), and executes actions such as group administration (anti-link, anti-badword, welcome messages, warn/kick), media downloads (YouTube, TikTok, Instagram), AI chat (via Groq/Llama), image/sticker editing, and privacy toggles. The bot maintains persistent settings in a PostgreSQL database (with a JSON file fallback), including global and per-group configurations, warn limits, banned users, and conversation history for AI context. It runs as a long-lived process with auto-reconnection, an Express health server, and supports deployment on Heroku, Railway, and traditional Node.js hosts. Architecturally, the bot is a monolith with a central message router in `src/toxic.js`, a dynamic plugin loader in `handlers/commandHandler.js`, and a set of background features (`features/`) that listen to events like group joins, sticker sends, and anti-spam triggers. The codebase is moderately complex, using global state objects (e.g., `_toxicMsgCounts`, `lidPhoneCache`) and patching the Baileys library at startup to adjust timeouts and event buffering. External dependencies include Express, Groq API, various download services (Nexray, qu.ax, uguu.se), and media utilities (ffmpeg, sharp, wa-sticker-formatter). The bot's command structure is consistent: each plugin exports `name`, `aliases`, `description`, and a `run(context)` function, enabling extensibility. However, the code exhibits several quality issues: no test suite, heavy use of global variables, hardcoded developer phone numbers, repetitive toggle commands, and obfuscated API keys in `keys.js`. Despite these shortcomings, the bot is functional and widely forked (1587 forks), indicating practical utility in the WhatsApp bot community.

The LLM identified 2 files worth highlighting for reuse: