Back to skill

Security audit

Superpowers Systematic Debugging

Security checks for vulnerabilities and agentic risk

Overview

This is a Markdown-only debugging workflow skill with broad activation wording and Chinese-only content, but it does not request hidden access, persistence, code execution, credentials, network use, or destructive behavior.

Install this if you want an opinionated, Chinese-language systematic debugging checklist. Be aware it may activate for many routine engineering issues and may slow quick fixes by requiring root-cause investigation first.

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

Natural-Language Policy Violations

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The skill content is entirely written in Chinese, while there is no indication that the user requested Chinese output or that this is a region-specific skill. This creates a language policy concern because it implicitly enforces a specific language without offering user choice or documenting a justified locale constraint.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The manifest description says to use the skill when encountering "any bug, test failure, or unexpected behavior," which is a very broad trigger likely to overlap with many ordinary development situations. It does not define clear boundaries for when this skill should activate versus when other troubleshooting or domain-specific skills should be used.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The "何时使用" section says the skill is for "任何技术问题" and then lists many common situations like test failures, bugs, performance issues, build failures, and integration issues. This makes activation ambiguous because it effectively covers most engineering problems and provides no limiting conditions or negative examples.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.