Back to skill

Security audit

frontend-ui-system

Security checks for vulnerabilities and agentic risk

Overview

This is a frontend UI design guidance skill with broad activation wording, but it does not contain hidden execution, persistence, credential handling, network access, or destructive behavior.

Install only if you want an opinionated frontend/UI design workflow. Be aware it may activate on vague requests like making something look more modern or professional, so clarify when you do not want UI redesign guidance applied.

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

Vague Triggers

High
Confidence
98% confidence
Finding
The skill instructs activation on vague phrases like 'hazlo más moderno' or 'quiero una UI bonita,' which are common, ambiguous requests that may appear in many contexts. This makes unintended invocation substantially more likely, allowing the skill to steer agent behavior based on broad heuristics rather than clear user consent, which is dangerous in systems that compose multiple skills.

Vague Triggers

Medium
Confidence
93% confidence
Finding
The skill defines activation triggers very broadly for common UI-related requests without clear scoping boundaries, so it may be invoked in many situations where specialized frontend/design behavior was not intended. Over-broad activation increases prompt-routing risk, can override more appropriate skills, and may cause the agent to apply hidden behavioral instructions to unrelated requests.

Static analysis

No suspicious patterns detected.