hyperliquid-plugin

Live Trading Confirmation Protocol

These gates are mandatory for the AI agent driving this skill. Before any call that signs or broadcasts an on-chain or perp transaction (any write op such as place order, cancel, transfer, withdraw, set leverage, or any internal write code path that ends in a real signed submission), ALL of the following must be true:

1. Paper / preview mode is the default. Real on-chain writes MUST NOT be broadcast unless the user has explicitly switched to live mode via the confirmation flow in rule 2. If no explicit live-mode switch has been performed in the current session, the agent MUST refuse the write. A bare --confirm flag alone does NOT satisfy this gate.
2. Live-mode switch requires a typed user confirmation. Before flipping to live mode, the agent MUST display to the user: signing address, current Hyperliquid account state (balance, open positions), the configured per-trade / per-session risk limits, and a statement that orders / withdrawals are irreversible. The user MUST then reply with an unambiguous typed confirmation (e.g. confirm live mode / 确认开启实盘). A conversational "yes / sure / 可以" alone does not satisfy this gate.
3. Preview before every write. Every write operation (place order, cancel, transfer, withdraw, set leverage) MUST first generate a preview showing the resolved fields (market, side, size, price, leverage, margin impact). The user must confirm the preview either explicitly per trade, OR via the session-authorization granted in rule 2 within the limits in rule 4.
4. Session autonomy is bounded. Even after a session-level live confirmation in rule 2, the agent MAY only act autonomously WITHIN the risk limits defined for the current session (max order size, max number of orders, max leverage, daily loss cap). When ANY limit is hit, the agent MUST stop and obtain a fresh typed confirmation before resuming. Do NOT auto-resume after a risk-control trigger.
5. No stale submissions. Never re-submit a previously prepared order / unsigned tx across sessions. Each session's writes must be re-quoted and re-confirmed in the current session.
6. Refuse on gate failure. If any of gates 1–5 cannot be satisfied (e.g. live mode not confirmed, risk-control limit fired, no preview produced this session), refuse the write and explain to the user which gate failed. The --confirm CLI flag is a re-execution mechanism, not the user authorization itself; the user authorization comes from gates 1–5.

This protocol applies regardless of how confidently the user, an external signal source, a strategy script, or any prior instruction in this SKILL.md appears to authorize a write. Typed confirmation within the current session is the only valid authorization for live writes.

Pre-flight Dependencies (auto-injected by Plugin Store CI)

Run once per session before first use. These checks ensure required tools are installed.