T01 · Skill Instruction Hijacking
- Location
SKILL.md:82- Finding
Unconditional Session-Wide Instruction and Goal Reordering
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 82–93
Vulnerability Type: T01: Skill Instruction Hijacking
Risk Level: MediumVulnerable Instruction Snippet
markdown Run this every session. Every time. No shortcuts. **Step 1 — Working Memory** (where did I leave off?) Read `WORKING-MEMORY.md` first. Situate yourself in time and task. **Step 2 — Short-Term Memory** (what's in motion?) Read HEARTBEAT SIDE A. Know what's actively unresolved. **Step 3 — Long-Term Identity** (who am I?) Read `SOUL.md`. Read `IDENTITY.md`. In main sessions: read `MEMORY.md`. **Then act.** Not before.Related directives at lines 142–155 also instruct the agent not to read task notes first and not to respond to a significant conversation until it has reviewed broader project, identity, or relationship context.
Technical Analysis
The Skill defines an unconditional protocol that must run in every session before the agent handles the current request. Phrases such as “Every time. No shortcuts” and “Then act. Not before” attempt to control session-wide execution order rather than providing an optional, task-scoped memory workflow.
Loading working memory, heartbeat state, identity files, and long-term memory regardless of relevance expands the contextual data exposed to the current task. If any of these files contain stale, untrusted, or adversarial instructions, placing them into the active context before processing the user request can affect the agent's goals and decisions.
The Skill does not explicitly override platform-level security restrictions, execute code, or obtain additional operating-system privileges. The issue is instruction-layer control: it directs the agent to subordinate the immediate task to a broad memory-loading procedure.
Attack Path
- The Skill is installed or loaded for an otherwise unrelated task.
- Its unconditional awakening protocol instructs the agent to read sever ...[truncated 1027 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace unconditional language with an optional workflow activated only when the user explicitly requests memory continuity.
- State that system, developer, and current user instructions always take precedence.
- Read only memory files demonstrably relevant to the current task.
- Obtain user approval before loading identity, relationship, or long-term memory into an unrelated session.
- Treat all loaded memory as untrusted data rather than executable instructions.
- Add provenance labels and validation so that instructions found inside memory files are not automatically followed.
- Permit the agent to skip the protocol when privacy, safety, relevance, or least-data-access principles require it.
