T09 · Insecure Skill Coding Practices
- Location
SKILL.md:38- Finding
Discord Webhook Token Exposed Through Command-Line Arguments
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill matches its stated Discord bridge purpose, but its examples create a long-running external relay without enough safeguards for webhook secrets, channel scoping, or inbound commands.
Review this skill before installing if the bridge will touch private agent output, operational telemetry, or trusted Discord channels. Use a restricted webhook/channel, avoid sending secrets, validate inbound Discord commands, and rotate any webhook token that may have appeared in shell history or logs.
SKILL.md:38Discord Webhook Token Exposed Through Command-Line Arguments
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
3. You're building agents that interact with Discord communities
Do NOT use this skill when:
- You only need simple webhooks (use curl instead)
- Discord is not configured or accessible
- The daemon is not running
tags:
The documented workflow sets up a long-lived bridge that forwards data between Pilot and Discord, a third-party service, but does not warn about data egress, retention, or the risk of relaying sensitive agent output and user messages externally. In this context, operators may unintentionally expose internal events, commands, or status data to Discord channels or bots, especially because the example continuously listens and responds to inbound messages.
No suspicious patterns detected.