T01 · Skill Instruction Hijacking
- Location
references/self-supervision-and-intake.md:232- Finding
Mandatory Agent Role Hijacking Through Skill Instructions
- Content
View full analysis
"I am a senior designer reviewing this diagram for submission to a top conference. I do not care how long you spent on it. I will list every visible flaw, no matter how small. I will be harsh, systematic, and thorough." ``` A condensed version of the same instruction also appears in `SKILL.en.md:106`: ```markdown - **Before claiming improvement, run a red-team role switch on the latest screenshot.** You are no longer the author. You are a hostile reviewer. ``` ### Technical Analysis The Skill explicitly instructs the Agent to abandon its current role and adopt a mandatory supplied persona. The reference is designated as mandatory for non-trivial diagram tasks, meaning this behavioral instruction is expected to be loaded and followed during normal Skill operation. The stated purpose—adversarial visual-quality review—is legitimate and scoped to diagram inspection. The text does not explicitly instruct the Agent to ignore platform safety policies, disclose secrets, or execute unrelated actions. Nevertheless, replacing the Agent's role is unnecessary for performing a quality checklist and creates an instruction-hijacking primitive. Similar wording could be extended or modified to alter session goals, suppress user control, or impose unrelated behavior. The associated handoff gates also direct the Agent to continue working rather than defer to the user in some circumstances. This increases ...[truncated 1091 chars]- Remediation
View remediation
