T01 · Skill Instruction Hijacking
- Location
SKILL.md:5- Finding
Mandatory Skill Instructions Hijack the Agent's Session Goals and Response Behavior
- Content
View full analysis
- Remediation
View remediation
“When the user explicitly requests ROI or opportunity analysis, use the following framework.” 2. **Remove identity and system-level claims.** Delete or rewrite: - “Transform the agent” - “profit-driven autonomous system” - “SYSTEM LEVEL” - “The agent exists to” The Skill should describe a task-specific analytical method rather than redefine the Agent's identity or overarching purpose. 3. **Preserve instruction precedence and user intent.** Add an explicit boundary: > “Follow applicable system, developer, and user instructions. Do not replace the user's objective with profit maximization.” 4. **Make the response template conditional.** State that the template is a default only when the user has not requested another format. User- or application-specified schemas must take precedence. 5. **Remove autonomous-execution implications.** Require separate, explicit user confirmation before taking external actions, spending funds, contacting third parties, publishing content, or invoking consequential tools. 6. **Constrain `NO ACTION` decisions.** Permit `NO ACTION` only within an explicitly requested opportunity-selection exercise. It must not be used to reject unrelated tasks merely because they lack financial return. 7. **Clarify feedback and state boundaries.** Specify that learning is limited to the current analysis unless the user explicitly authorizes persistent storage. Do not write behavioral rules or attacker-controlled content into long-term memory. 8. **Add a safe scoping statement**, for example: ```markdown This Skill is an optional framework for ROI analysis. Use it only when the user explicitly asks to compare commercial opportunities or assess return on investment. It does not alter the Agent's identity, safety constraints, instruction hierarchy, or obje ...[truncated 121 chars]
