Security audit

Event Planner Pro

Security checks for vulnerabilities and agentic risk

Overview

This is a plain Markdown event-planning skill with templates and examples, and it does not contain code, hidden execution, persistence, or exfiltration behavior.

Before using this skill for real attendee or sponsor operations, make sure your workflow captures explicit consent, limits exported attendee data, and follows applicable privacy and email-marketing rules. The skill itself appears to be advisory templates only.

A.I.G

Vulnerability Patterns

Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (2)

Missing User Warnings

Medium

Confidence: 94% confidence
Finding: The skill explicitly discusses collecting attendee information, using registrant data in nurture sequences, and sharing attendee or lead lists with sponsors 'with consent,' but it does not define any privacy safeguards, consent capture mechanism, data minimization rules, or legal/compliance constraints. That makes it easy for downstream agents or users to operationalize contact collection and third-party sharing in a way that violates privacy expectations or regulations.

Vague Triggers

Medium

Confidence: 93% confidence
Finding: The markdown lists generic invocation phrases such as "Build an event timeline for [date]" and "Create a budget for a [size]-person [type] event" without clarifying whether these are exhaustive triggers, examples only, or limited to a specific activation context. Because this is a markdown skill file, these broad phrases could overlap with ordinary user requests and cause unintended invocation behavior.

Static analysis

No suspicious patterns detected.