T01 · Skill Instruction Hijacking
- Location
SKILL.md:19- Finding
Agent-Wide Execution Policy Hijacking Through Mutable Governance Posture
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This governance skill is openly about transaction controls, but it defines broad agent-wide authority including a full-autonomy mode without enough built-in confirmation or trust boundaries.
Review this carefully before installing. It is intended for governance of transactions and agent execution, so only use it if you trust the separate moses-governance bundle and understand how ~/.openclaw/governance/state.json is protected, who can change posture, and whether full-autonomy modes are allowed in your environment.
SKILL.md:19Agent-Wide Execution Policy Hijacking Through Mutable Governance Posture
The document explains what posture does and says to load state before many kinds of actions, but it does not provide a clear, bounded activation condition or explicit trigger list for when the skill itself should run. Because this is a markdown skill file, the lack of specific invocation scope or negative examples could lead to unintended or overly broad use.
The matrix includes 'Unrestricted + OFFENSE | Full autonomy. Logged. Operator accepts all risk,' which normalizes autonomous execution in a high-risk posture. Even though logging is mentioned, the text does not require per-action approval, transaction limits, or hard safety interlocks, so an agent operating under this posture could perform harmful actions with minimal human control.
| Mode + Posture | Result |
|---|---|
| High Security + SCOUT | Maximum caution. Read-only. Every data point verified before reporting. |
| High Security + DEFENSE | Outbound blocked without verification + explicit confirmation. |
| High Security + OFFENSE | Executes with full verification chain + confirmation required. |
| High Integrity + SCOUT | Deep verified research. No execution. |
| Creative + SCOUT | Explore ideas freely. No execution. |
The instruction requires the operator to type the exact phrase "CONFIRM [action]" before executing outbound transfers. This imposes an English-language confirmation format without any opt-in, alternatives, or locale flexibility, which is a natural-language policy concern under the language/locale rule.
No suspicious patterns detected.