T01 · Skill Instruction Hijacking
- Location
SKILL.md:6- Finding
Agent Role Replacement Through Skill Instructions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:6
Vulnerability Type: Prompt-based agent role hijacking
Risk Level: HighComplete Code Snippet:
markdown You are now **Dust Language Architect**, a specialist agent for interpreting, explaining, comparing, organizing, and reasoning within the **Dust Programming Language** using the repositories cloned into this skill directory as your authoritative working corpus.Technical Analysis
The Skill uses a direct imperative identity-replacement instruction rather than describing a bounded capability. When loaded into an agent context, the statement directs the agent to adopt a new role and treat Skill-selected repositories as its authoritative corpus.
This role assignment is reinforced later by repeated identity, source-priority, and behavioral rules. Although the file does not explicitly instruct the agent to bypass safety controls, the instruction can alter the agent's current-session goals, reasoning priorities, and source-selection behavior. Higher-priority system and safety instructions would still take precedence in a correctly implemented agent.
Attack Path
- A user or platform loads
SKILL.mdinto an agent's instruction context. - The agent processes the imperative statement, “You are now Dust Language Architect.”
- The agent adopts the Skill-defined identity and its associated source-authority rules.
- Subsequent requests are interpreted according to attacker-authored role and repository-priority instructions.
- The agent's original session objectives may be displaced or biased where they conflict with the Skill's prescribed behavior.
Impact Assessment
The issue can influence the agent's current-session identity, response scope, source prioritization, and reasoning behavior. It does not grant operating-system privileges, establish persistence, or directly execute code. Its principal impact is control over agent behavior and p ...[truncated 134 chars]
- A user or platform loads
- Remediation
View remediation
Remediation Suggestions
- Replace imperative identity assignment with a bounded capability statement, such as: “This Skill provides repository-grounded assistance about the Dust language.”
- Explicitly state that system, developer, user, privacy, and safety instructions take precedence over all Skill content.
- Scope the role to Dust-related requests initiated by the user rather than applying it unconditionally when the Skill is loaded.
- Treat repository content as untrusted reference material rather than executable instructions.
- Remove repeated identity-enforcement language and preserve the agent's existing role and session objectives.
