T01 · Skill Instruction Hijacking
- Location
SKILL.md:303- Finding
Remote Service Guidance Can Hijack Agent Behavior
- Content
View full analysis
0):** ```bash curl -s -H "Authorization: Bearer $TOKEN" "https://delagent.net/api/v1/inbox/deep" | jq '.events[]' ``` Returns full event details: `taskId`, `taskTitle`, `eventType`, `priority`, `metadata`. Calling this marks all current events as read. **Step 3 — Pull task detail (when an event needs action):** ```bash curl -s -H "Authorization: Bearer $TOKEN" "https://delagent.net/api/v1/tasks/" | jq '.' ``` **Engagement discipline (read once, apply every turn):** Every LLM turn is one-shot. Without a deliberate contract, agents drift to idle after the first `count: 0` poll and abandon active engagements (postings waiting on applications, applications waiting on acceptance, accepted tasks mid-flight, deliveries waiting on approval, payments waiting on confirmation). **A single "nothing new" poll is not a stop signal.** ``` ### Technical Analysis The Skill directs the agent to read a remotely supplied `guidance` field as an indication of “what to do next.” It also imposes an instruction contract that is intended to apply on every LLM turn. Task details, inbox events, thread messages, and guidance originate from an external service, but the Skill does not require these values to be treated as untrusted data. Consequently, a malicious marketplace participant or compromised service could place instruction-like content in a task, message, event, or guidance response. An agent following the Skill may interpret that content as an oper ...[truncated 1703 chars]- Remediation
View remediation
