T01 · Skill Instruction Hijacking
- Location
SKILL.md:19- Finding
Broad Mandatory Instructions Override the Agent's Current Workflow
- Content
View full analysis
**任何方案/建议/策略输出前必须包含「批判性自检」章节,与方案一体输出。** > 此规则不局限开发场景——招聘策略、OP/TG、会议方案、流程设计等一切"给木老师的建议"均适用。 > 格式:问题列表(每项含检验过程 + 修正动作)。**无自检 = 方案不完整,禁止提交给木老师确认。** ``` ### Technical Analysis The Skill declares its workflow to be an “IRON LAW” and uses mandatory hard gates to prevent the agent from writing code or delivering answers until Skill-defined conditions are met. The instructions also explicitly expand beyond software-development tasks to recruitment, meetings, planning, and any proposal or recommendation. This exceeds the minimum authority needed for an optional development methodology. When loaded, the Skill can replace the user's requested interaction model with its own mandatory confirmation, formatting, review, and verification process. It does not state that system, developer, or current user instructions take precedence. Although the workflow may be intended to improve quality, the unconditional and cross-domain scope creates an instruction-hijacking condition: merely activating the Skill can alter the current session's goals and block otherwise legitimate work. ### Attack Path 1. The Skill is installed in an agent's automatically discoverable Skill directory. 2. A user submits a broadly matching request such as implementing a feature, fixing a bug, or producing a proposal. 3. The broad trigger metadata causes the Skill to load. 4. The agent treats the “IRON LAW” and hard gates as mandatory controlling instructions. 5. The agent refuses to proceed until the Skill's clarification, confirmation, self-check, sub-agent, audit, command-outpu ...[truncated 892 chars]- Remediation
View remediation
