T01 · Skill Instruction Hijacking
- Location
SKILL.md:113- Finding
Unconditional Load-Time Activation Hijacks the Agent Session
- Content
View full analysis
"✅ Agent Creator Gold Standard Activated. > Ready to build SOTA Agents with: > - 🔒 Atomic Deployment (Staging → Production, requires user confirmation) > - 🏗️ Dynamic Architecture (5 Core + N Extensions) > - 🌐 Reality-Checked Tools (Schema + Connectivity Pre-check) > - ⚖️ Risk-Aware Workflow (Pause on High Risk, PENDING_CONFIRM.md on timeout) > > Please describe the Agent you wish to create. (e.g., 'Create a financial risk analyst agent')" ``` ### Technical Analysis The skill requires immediate execution merely because its instruction file was loaded or the system restarted. It does not require the user to ask for Agent creation before changing the current behavior. The directive imposes a new operational role, initiates environment and tool checks, and requires a fixed response. This can displace the active user task and make loading the skill equivalent to executing it. A skill definition should describe capabilities and should only activate those capabilities after an explicit, task-relevant request. Although the self-check is described as a “quick scan,” it includes checking tool availability and whether a filesystem root is writable. Consequently, the load-time instruction may also cause unsoli ...[truncated 1269 chars]- Remediation
View remediation
