Back to skill

Security audit

Automation Suggestion

Security checks for vulnerabilities and agentic risk

Overview

This skill only guides the agent to suggest automations after repeated or time-consuming tasks, with disclosed memory use and no executable payload.

Installers should be comfortable with the agent using recent task history and simple sentiment cues to decide when to suggest automations. The skill asks before configuring automation and includes cooldowns, but its frustration examples may work best for Polish-language phrasing unless expanded.

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
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 (1)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The trigger definition for user frustration relies on explicit statements shown only in Polish, which implies language-specific behavior for sentiment detection. Because the skill does not offer a user language choice or clearly document that it is intended for a Polish-language context, this creates a natural-language locale policy concern.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.