T09 · Insecure Skill Coding Practices
- Location
SKILL.md:166- Finding
Caller-Controlled Priority Can Bypass Notification Rate Limiting
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a legitimate notification skill, but it needs Review because it can send real outbound messages and has weak safeguards around recipients, rate-limit bypass, logs, and links.
Review before installing in any environment that can actually send messages. Replace the example recipients with placeholders, require explicit operator confirmation for sends and broadcasts, validate or generate all links server-side, enforce consent and opt-outs, protect or minimize delivery logs, and avoid letting callers choose high priority without authorization and bounded quotas.
SKILL.md:166Caller-Controlled Priority Can Bypass Notification Rate Limiting
templates/email/invoice.md:57Unvalidated Template URLs Enable Phishing and Unsafe Link Injection
To unsubscribe from these emails, please contact us or click here.
``` `templates/email/notification.md:17-20`: ```html {{#if cta_url}} {{/if}} ``` `templates/email/notification.md:25-28`: ```htmlTo unsubscribe, click here.
``` `templates/email/welcome.md:25-28`: ```html {{#if cta_url}} {{/if}} ``` `templates/email/welcome.md:35-38`: ```htmlTo unsubscribe from these emails, click here.
``` `templates/telegram/broadcast.md:1 ...[truncated 2492 chars]SKILL.md:58Executable Examples Contain Hard-Coded Real-Looking Recipient Identifiers
This markdown file describes immediate and scheduled sending of notifications to external channels like WhatsApp and Telegram, including explicit recipient targets. It also documents delivery logs containing channel and target data, but provides no warning that using the skill transmits recipient/system data to third-party services and stores identifying contact information in local logs.
The skill operationalizes outbound messaging across multiple channels and stores queue and delivery data, including recipient identifiers and message content variables, but it provides no privacy, consent, retention, or access-control guidance. In this context, that omission can lead agents or operators to process personal data, send messages without adequate authorization, and retain sensitive metadata in logs, increasing compliance and data exposure risk.
This file applies quiet hours using the fixed timezone "America/Los_Angeles", which imposes a locale-specific behavior on all users unless overridden elsewhere. Under the policy, forcing a specific locale without user opt-in is a natural-language policy concern even in configuration files.
This manifest advertises promotional broadcast templates such as "Broadcast Promotion" but provides no disclosure in the file about the user-impacting nature of sending marketing content. For markdown and manifest-style descriptions, safety-sensitive behaviors that can affect privacy or user communications should be accompanied by clear warnings or usage constraints.
No suspicious patterns detected.