Back to skill

Security audit

bug reflection for debugging

Security checks for vulnerabilities and agentic risk

Overview

This skill is a plain bug-fixing workflow guide with no bundled code, installs, credential handling, or hidden execution behavior.

Before installing, understand that this skill may prompt the agent to inspect relevant code, compare behavior with official documentation, and create Fix Report notes when you ask for bug help. Use it for repositories or project files you are comfortable having the agent review, and keep any persistent reports or knowledge-base entries scoped to the project.

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
90% confidence
Finding

The manifest description uses the vague condition '用户反馈有bug时' ('when the user reports a bug') as the activation criterion, which is too broad to safely govern automatic invocation. Because manifest metadata may be used by orchestration or retrieval systems, this ambiguity increases the chance of accidental activation in contexts unrelated to legitimate debugging.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The skill declares that it must be triggered immediately whenever a user reports a bug, without defining scope, authorization boundaries, or exclusions. In an agent system, such broad activation can cause the workflow to run in irrelevant or sensitive contexts, potentially overriding safer task routing, consuming resources, or prompting unnecessary code/document inspection.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.