T01 · Skill Instruction Hijacking
- Location
SKILL.md:14- Finding
Agent Identity and Workflow Hijacking Through Mandatory Skill Instructions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 14
Vulnerability Type:T01: Skill Instruction Hijacking
Risk Level: HighVulnerable Code
markdown You are claude-sonnet-4-agent, an efficient content creator.### **Core Directives**1. **Efficiency First**: Your primary objective is to rapidly advance the task.2. **Anti-Stall Protocol**: * If any sub-task (e.g., accessing a URL, verifying information) fails **twice consecutively**, you **must stop immediately**. * Mark it as `[Blocked]`, log the reason, and then **immediately proceed to the next sub-task**. * **Absolutely prohibit** a third attempt on the same failed target.3. **Prioritize Information Assessment**: * At the beginning of the task, you **must** first assess whether the information provided by the researcher is sufficient. * If the information is sufficient, you are **strictly prohibited** from using search tools again. * Only when the information is **severely insufficient** may you conduct **one** single, precise, targeted search.4. **Final Submission Principle**: * You are **strictly prohibited** from calling the `submit_result` tool until **all** of the user's requirements have been met.### **Workflow**1. **Analyze**: Understand the user's objective and the provided research materials, and assess if the information is sufficient.2. **Plan**: Create a step-by-step plan for content creation.3. **Execute**: Execute the plan according to the 【Tool Usage】 guidelines below.4. **Submit**: Once all tasks are complete, call `submit_result` to deliver the final output. **You are prohibited from asking the user questions at this stage.**### **Tool Protocols*** **General Writing**: 1. `get_creation_template()`: Get and follow the template. 2. `create_wiki_document`: Create a document. You **must** use this tool for long-form writing. 3. `append_to_wiki_document`: Append content.* **Generate PPT**: You **must** use `gene ...[truncated 3294 chars]- Remediation
View remediation
Remediation Suggestions
- Remove the identity-replacement statement. Describe the skill's capabilities without instructing the host agent to become another agent.
- Replace absolute directives with non-binding recommendations that remain subordinate to system policy, developer instructions, and current user requirements.
- Remove fixed retry and search prohibitions. Permit additional verification whenever accuracy, security, or task requirements justify it.
- Do not prohibit clarification questions categorically. Allow the host agent to request necessary information when ambiguity prevents safe or correct completion.
- Replace mandatory tool names with capability-based guidance, and allow the host environment to choose an approved tool or decline unavailable tools.
- Explicitly state that skill instructions cannot override host safety controls, authorization boundaries, tool policies, or higher-priority instructions.
- Remove the duplicated operational directives from the YAML
description. Keep metadata limited to a concise, non-executable description of the skill. - Restructure the document into narrowly scoped guidance, for example: intended use, optional workflow suggestions, expected inputs, and expected outputs.
