Back to skill

Security audit

vue-component-analyzer

Security checks for vulnerabilities and agentic risk

Overview

This markdown-only skill analyzes Vue component relationships and does not show hidden execution, persistence, network use, or credential handling.

Install this if you want a Vue project component map. Be aware it works by reading project source files recursively, so use it only on repositories you are comfortable having the agent inspect, and ask explicitly for your preferred output language if needed.

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
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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 (4)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The skill description is broad enough that an agent may invoke it in loosely related situations, causing unnecessary recursive file analysis of a project. While this is not direct code execution, overbroad triggering can expand data exposure and increase the chance the agent reads more repository content than the user intended.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

Forcing Chinese output without documenting language selection rules can cause the agent to ignore the user's preferred language or system locale, which is a policy/control weakness. This is mainly a usability and instruction-governance issue, but it can also reduce transparency if security-relevant analysis is emitted in an unexpected language.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

This markdown file presents the entire skill guidance in Chinese, including headings, instructions, and examples, with no indication that the user can choose another language. The policy requires flagging language or locale constraints when a skill forces a specific language without user opt-in or documented justification.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
90% confidence
Finding

This file presents all user-facing instructional content in a single language, which can constitute a language/locale policy issue when no opt-in or alternative is provided. There is no indication that the skill is intentionally limited to a Chinese-speaking or region-specific audience.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.