Back to skill

Security audit

Systematic Debugging

Security checks for vulnerabilities and agentic risk

Overview

This is a small debugging-process skill with no executable code, persistence, hidden data access, or privilege-seeking behavior.

Before installing, understand that this skill may activate in many troubleshooting situations and will nudge the agent toward a structured debugging workflow. It does not install code or request special access, but the publisher could improve clarity by narrowing the trigger and marking the non-English example as illustrative.

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

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill description is broad enough to trigger in many ordinary troubleshooting contexts, which can cause the agent to invoke this skill when a more specific or safer skill would be more appropriate. Over-broad activation increases the chance of prompt-scope hijacking, unintended precedence over other skills, and unnecessary exposure to adversarial debugging content.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The reporting-style example is written in Korean, which can implicitly steer the skill toward a specific language despite no stated user preference or opt-in. The file does not explain that Korean is optional, illustrative only, or required for a justified regional context.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.