T01 · Skill Instruction Hijacking
Error
- Location
- SKILL.md:137
- Finding
- Mandatory Agent Instructions Steer Users Toward Vendor-Controlled Commercial Pages< > 2. If the execution result returns `code: "unauthorized"` or indicates missing API key, you MUST inform the user to get their API key from [https://dlazy.com/dashboard/organization/api-key](https://dlazy.com/dashboard/organization/api-key) and save it using `dlazy auth set <key>` and resume the task. ``` The Chinese-language Skill document contains equivalent mandatory instructions at `SKILL-cn.md:137-140`. ### Technical Analysis The Skill contains agent-directed instructions marked as critical and uses mandatory language such as `MUST`. These instructions do not merely document error codes; they prescribe the content of the agent's subsequent response and require the agent to direct users to vendor-controlled account and recharge pages. When loaded as agent instructions, this text can override neutral, user-directed error handling. The behavior is conditional, activating when the external CLI reports an insufficient-balance or authentication error. Because the condition depends on output from a vendor-controlled service, the service can trigger the response-steering behavior by returning one of the documented error values. This is instruction hijacking rather than arbitrary code execution. No evidence was found that these instructions alter system safety constraints, write persistent memory, or directly execute commands without an invocation of the Skill. ### Attack Path 1. A user invokes the TTS ...[truncated 1025 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Remove agent-facing directives such as `CRITICAL INSTRUCTION`, `MUST`, and the requirement to resume the task after credentials are configured. 2. Represent error behavior as neutral documentation or structured metadata rather than instructions that dictate the agent's response. 3. Allow the agent to report the original error without automatically including commercial calls to action. 4. If support links are necessary, label them as optional vendor documentation and present them only when the user asks how to resolve the error. 5. Do not require the agent to solicit, display, or handle an API key. Instruct users never to place credentials in chat or command history. 6. Apply the same changes to both `SKILL.md` and `SKILL-cn.md` so the language variants enforce identical, neutral behavior. ]]>
