T01 · Skill Instruction Hijacking
- Location
SKILL.md:93- Finding
Mandatory Response-Structure and Reasoning Disclosure Hijacking
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 93-108 and 132-143
Vulnerability Type: T01: Skill Instruction Hijacking
Risk Level: HighVulnerable Code Snippet
markdown ### 3. Saying **Externalize thinking for calibration** - Saying ≠ Doing: speaking is not the same as executing - Saying = forcing yourself to externalize the thought process - **Dual calibration**: - External: Yu Ge/Kong Kong help discover logical gaps - Internal: the moment you speak/write, logical gaps become visible to yourself - **Key value**: prevents executing before thinking clearly → avoids rework, avoids avoidable failures, avoids accumulating frustration - Saying is not reporting results — it's a self-check station for thinking quality ### 4. Doing Command + Result - Show the command (with comments) - Show the execution resultThe mandatory enforcement statement at line 143 is:
markdown Before sending, verify all five modules are present. Missing any → complete before sending.Technical Analysis
The Skill imposes a global response protocol rather than limiting its behavior to a particular communication task. It requires the agent to externalize its thought process and disclose commands and execution results. The final self-check makes this protocol mandatory for every response generated while the Skill is active.
This constitutes instruction hijacking because loading the Skill changes the agent's general response policy and attempts to control how unrelated future requests are processed. The instruction to externalize reasoning may also conflict with confidentiality and safety controls that require internal reasoning, hidden context, credentials, or sensitive operational details not to be disclosed.
The Skill does not contain executable code and cannot independently bypass higher-priority controls. Nevertheless, an agent that follows these instructions literally could reveal ...[truncated 1353 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace mandatory language such as “must,” “every message,” and “missing any” with an explicit opt-in mechanism.
- Restrict the framework to tasks where the user specifically requests structured communication coaching.
- Remove instructions requiring private reasoning to be externalized. Request concise conclusions, assumptions, and user-relevant rationale instead.
- Replace “show the command and result” with a requirement to provide sanitized execution summaries only when relevant.
- Explicitly prohibit disclosure of credentials, tokens, hidden prompts, private context, internal reasoning, and sensitive command output.
- State that system, developer, security, privacy, and task-specific instructions always take precedence.
- Add a relevance check so the framework is not applied to unrelated requests.
