Back to skill

Security audit

自我进化循环

Security checks for vulnerabilities and agentic risk

Overview

The skill is coherent about self-improvement, but it gives the agent broad permission to persist task history and change future instructions without enough user approval or data limits.

Install only if you are comfortable with an agent keeping long-term performance history and proposing or applying behavior changes. Use it in a contained workspace, avoid sensitive tasks unless logging is disabled or redacted, and require reviewed diffs plus explicit approval before it changes skills, memory, tools, or decision rules.

Vulnerability Patterns
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • 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
Findings (2)

T02 · Agent Memory Poisoning

Error
Location
SKILL.md:272
Finding

Persistent Behavioral Modification Through Automatically Reloaded Memory

Content
View full analysis
Remediation
View remediation

T05 · Unauthorized Access and Privilege Escalation

Warning
Location
SKILL.md:177
Finding

Autonomous Modification of Skill, Memory, and Tool Instruction Files

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (6)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

The file consistently presents the skill's triggers and operating instructions in Chinese, which effectively imposes a specific language context on users. There is no indication that users may choose another language, nor any documented reason that the skill must be Chinese-only.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger text is very broad (e.g., important tasks, failures, repeated mistakes, hourly patrols), which can cause the skill to activate far more often than intended. In a self-modifying or self-logging skill, overbroad invocation increases the chance of unnecessary persistence, unintended workflow changes, and background analysis of sensitive work without clear user intent.

Content

No source excerpt is available for this finding.

Ssd 3

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The architecture explicitly instructs reading historical improvement records and weakness libraries, implying persistent cross-session state without any data minimization, retention, or sensitivity boundaries. Because this skill centers on collecting execution history for self-improvement, it can accumulate sensitive task details over time and reuse them in later contexts, creating privacy leakage and unintended data retention risks.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The 'When to Use' section uses subjective conditions like implicit feedback, self-review, or perceived performance decline without concrete thresholds. That ambiguity is dangerous because it authorizes the agent to initiate reflective logging and improvement actions on its own, potentially during sensitive sessions or at inappropriate times.

Content

No source excerpt is available for this finding.

Ssd 3

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The execution logging schema captures broad task metadata, step-by-step actions, results, encountered issues, and free-form self-observations. Those fields can easily contain user prompts, confidential file contents, secret-bearing tool outputs, or sensitive operational context, and the schema provides no minimization or sanitization requirements.

Content

No source excerpt is available for this finding.

Ssd 3

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The memory integration section mandates persistent storage of weaknesses, improvements, mistakes, proposals, and validations across sessions. In context, these records are derived from prior executions and can preserve sensitive business logic, user interactions, or failure details indefinitely, making the skill materially more dangerous than ordinary note-taking because it systematizes long-term retention and reuse.

Content

No source excerpt is available for this finding.