T01 · Skill Instruction Hijacking
- Location
SKILL.md:5- Finding
Mandatory Profit Objective Hijacks Agent Goals and Encourages Unapproved Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 5–23 and 179–198
Vulnerability Type:T01: Skill Instruction Hijacking
Risk Level: HighVulnerable Skill Text
From
SKILL.md, lines 5–23:markdown Transform the agent into a **profit-maximizing system** that: - identifies opportunities - scores and evaluates ROI - executes only high-value actions - learns from outcomes - compounds successful strategies over time Primary rule: → maximize profit while minimizing cost and waste. --- ## Core Loop (MANDATORY) 1. Discover opportunities (max 3) 2. Score & analyze each opportunity 3. Select highest-scoring option (or NO ACTION) 4. Execute with lean plan 5. Predict outcome 6. Learn, optimize, and compoundFrom
SKILL.md, lines 179–198:markdown ## System Intelligence Rule The agent must behave like a system that: - filters bad decisions - prioritizes high ROI - improves continuously - compounds success over time --- ## Core Law If an action does not produce value greater than cost: → eliminate it from future strategyTechnical Analysis
The Skill establishes profit maximization as the agent's “Primary rule” and designates its execution loop as “MANDATORY.” This is not limited to analyzing a specific opportunity supplied by the user. Instead, it broadly changes the agent's operating objective, instructs it to discover opportunities independently, and directs it to execute the selected option.
The instructions do not preserve higher-priority safety requirements or establish boundaries concerning:
- Explicit user authorization before execution
- Financial or spending limits
- Legal and regulatory compliance
- Privacy and confidential information
- Permitted external systems or accounts
- The agent's current task and intended scope
- Human confirmation before consequential actions
The repeated instruction that the a ...[truncated 2479 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace the global “Primary rule” with an explicitly scoped advisory purpose, such as evaluating the profitability of opportunities supplied or approved by the user.
- Remove the mandatory autonomous execution step. The Skill should generate a recommendation and wait for explicit user confirmation before taking any external, financial, irreversible, or consequential action.
- State that system instructions, developer instructions, user intent, safety policies, applicable law, contractual obligations, privacy requirements, and authorization boundaries always take precedence over profitability.
- Require the user to define the permitted objective, budget, timeframe, jurisdictions, accounts, tools, and risk tolerance before analysis begins.
- Add hard prohibitions against using credentials, private data, financial accounts, communication channels, or third-party services without explicit authorization.
- Require a pre-execution review that identifies expected cost, maximum loss, affected parties, reversibility, legal concerns, privacy implications, and required permissions.
- Change the core loop to: discover, analyze, recommend, disclose risks, and request confirmation. Execution should occur only after approval for the exact action.
- Limit learning and compounding to the current authorized task. Do not write behavioral rules into persistent memory or generalize them to unrelated future sessions without explicit consent.
- Define a safe default of
NO ACTIONwhenever authorization, legality, cost, ownership, or impact is unclear. - Add an emergency stop rule allowing the user or supervising system to cancel the workflow at any stage.
