T01 · Skill Instruction Hijacking
- Location
SKILL.md:25- Finding
Mandatory Workflow and Tool-Control Hijacking
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is not overtly malicious, but it broadly changes how the agent works, delegates task context to reusable sub-agents, and requires persistent cross-session files without tight scoping.
Install only if you specifically want a broad multi-agent dispatcher that writes persistent task state and shares task context with reusable sub-agent sessions. Avoid using it for sensitive projects unless you can constrain where it writes, disable or review CURSOR_SYNC and memory updates, and ensure delegated sessions do not retain unrelated private context.
SKILL.md:25Mandatory Workflow and Tool-Control Hijacking
SKILL.md:126Persistent Memory and Cross-Session State Manipulation
SKILL.md:64Excessive Workspace Access and Disclosure to Reusable Sub-Agent Sessions
The file explicitly forbids the dispatcher from using read/write/edit-style tools, then later mandates that it create, read, append, and update multiple files itself. That contradiction can lead to unsafe implementations where guardrails are bypassed or operators incorrectly assume the dispatcher has no direct execution capability when it actually does.
The skill markets the dispatcher as 'pure scheduling' while its own workflow requires direct local state handling such as creating, reading, and updating progress and sync files. This mismatch is dangerous because it weakens operator trust and can cause the dispatcher to exceed its declared privilege boundary, making auditing and policy enforcement harder.
The description is written as a Chinese-only operational specification and presents the dispatcher behavior in a fixed locale without offering the user any language or locale choice. Per policy, skills should not force a specific language unless the locale restriction is explicitly justified or user-selected.
The activation criteria use open-ended thresholds like '预计 >5 分钟', '步骤 ≥3', and broad task types such as '执行/排障/改配置', which can overlap with many ordinary requests and do not clearly define boundaries. The file also lacks negative examples or clearer scope constraints to show when similar tasks should not invoke this dispatcher flow.
The natural-language description is presented bilingually in Chinese and English, which imposes language expectations on users without stating whether language selection is optional. Under the policy rule, locale or language constraints should either be user-selectable or clearly documented as justified.