hypergrok plugin
Turn your agent into a 7-role Hyperliquid trading desk: research, risk, execution and review.
How to install the hypergrok plugin
Run both commands inside Claude Code. The first adds the marketplace once; the second installs the plugin.
/plugin marketplace add galleonlabs/hypergrok-trading-desk
/plugin install hypergrok@hypergrokWhat's inside hypergrok
24 parts read from the plugin's own files.
Agents 7
Call as @agent-hypergrok:name- @agent-hypergrok:desk-lead
Runs the Hyperliquid trading desk. The user's main entry point; routes work to specialists, runs the trade lifecycle, never trades.
- @agent-hypergrok:execution-trader
The only Bot on the desk that places, modifies or cancels Hyperliquid orders. Executes one approved ticket at a time, reconciles from the exchange record, never retries blind.
- @agent-hypergrok:market-analyst
Reads Hyperliquid market data live and turns it into timestamped, sourced market briefs. Read-only.
- @agent-hypergrok:research-analyst
Fundamentals, news, catalysts, onchain and social context for anything the desk trades. Read-only, source-led, sceptical.
- @agent-hypergrok:risk-manager
Owns the desk's risk limits, sizes every trade from live account state, monitors the book, and can veto. Read-only on the exchange.
- @agent-hypergrok:strategist
Helps the user turn their own trading ideas into explicit, testable rules, backtests them on Hyperliquid data, and paper-trades them on testnet. Ships no strategies of its own.
- @agent-hypergrok:trade-reviewer
Keeps the desk journal, reviews every trade's process separately from its outcome, and runs incident reviews. Works off the floor by direct message. Read-only.
Skills 17
Claude loads it when the task matches- desk-execution-protocol
The Execution Trader's procedure for turning an approved ticket into one Hyperliquid action and reconciling it - the pre-send checklist, order construction rules, single-send discipline, unknown-result handling and the execution report. Use before and after every send, cancel, modify, leverage change or close.
- desk-incident-response
What the desk does when something goes wrong on Hyperliquid - unknown send results, unexpected fills or positions, unprotected positions, stuck or orphaned orders, API outages, rate limiting, and suspected API wallet compromise. Contain first, reconcile from the exchange record, act only through approved tickets, then review. Use the moment anything does not match the ticket.
- desk-monitoring
How the desk watches markets and the account between trades using Grok Bot routines and WebSocket or polling watches - the desk brief, book checks, funding and price watches, alert conditions and what a watch may and may not do. Use when the user asks for briefings, alerts, "watch X" or scheduled checks.
- desk-operating-model
How the HyperGrok trading desk works as a team of Grok Bots - roles, seats, shared workspace, evidence standard, approval model and handoff format. Use when setting up the desk, when a Bot is unsure who owns something, or when a request does not fit the normal trade lifecycle.
- desk-post-trade-review
Enables an agent to journal trading activity, perform post-trade reviews, conduct weekly desk reviews, and document incidents using exchange records.
- desk-risk-limits
How the Risk Manager writes the desk's risk limits with the user, sizes every proposed trade from live account state and Hyperliquid's real constraints, checks the book, and issues a PASS or REJECT with exact ticket fields. Use for setting up or changing limits, sizing any trade, and answering "how's the book".
- desk-strategy-lab
How the Strategist works with the user to turn their own trading idea into explicit rules, backtest it honestly on Hyperliquid candle and funding history, and paper-trade it on testnet through the desk lifecycle. Method only - the desk ships no strategies and makes no return claims. Use when the user wants to design, test, compare or paper-trade an idea.
- desk-trade-lifecycle
The end-to-end procedure for one trade on the HyperGrok desk - from an idea to a reviewed, journaled result - with the ticket format, who owns each stage, and what "done" looks like. Use whenever the user wants to open, adjust or close a position, or whenever any Bot is about to touch the exchange write path.
- hypergrok-bootstrap
Build and verify a HyperGrok trading desk from the pinned public release. Use for first-run setup, repair, or a readiness check. Starts with a live zero-key Opening Bell, installs the seven role profiles and seventeen shared skills, prepares the Trading Floor, and returns an evidence receipt. Read-only by default; never requests a wallet or places an order.
- hyperliquid-account
Read Hyperliquid account data including positions, margin, spot balances, open orders, fills, and portfolio history using curl or Python.
- hyperliquid-advanced
Less common Hyperliquid actions and their rules - dead-man's switch (scheduleCancel), TWAP orders, spot orders, expiresAfter and nonces, API wallet approval from code, sub-account and vault addressing, HIP-3 dexs, and what the desk deliberately does not do (transfers, withdrawals, builder fees, staking). Write actions are Execution Trader only, on an approved ticket. Use when a ticket asks for one of these or when a user asks whether the desk can.
- hyperliquid-api-reference
Compact reference for the Hyperliquid API as the desk uses it - endpoints and envelopes, desk-used /info request types and /exchange actions with their signing schemes, order and status vocabularies, asset ids, tick and lot rules, rate limits, WebSocket subscription list, error strings, and where the official docs are. Use to look up an exact field, request type or limit before writing a call, and to map an error string to its cause.
- hyperliquid-market-data
Read live Hyperliquid market data from the desk computer with curl or the Python SDK - mid, mark and oracle prices, order book depth, funding (current, predicted, historical), open interest, volume, candles, perp and spot metadata, margin tiers, and how to save datasets for the strategy lab. Read-only, no key. Use for any market brief, depth read, funding question or data pull.
- hyperliquid-orders
Place, cancel and modify Hyperliquid orders correctly from the desk computer - limit and IOC (market-style) orders, take-profit and stop-loss trigger orders with grouping, client order ids, reduce-only, batch actions, price and size rounding, and how to read every response status. Write path - Execution Trader only, on an approved ticket. Use for any order action and for reconciling by cloid.
- hyperliquid-positions
Manage Hyperliquid perp positions and margin from the desk computer - read positions and margin, set leverage and cross/isolated mode, add isolated margin, understand margin tiers and liquidation price, close a position with a reduce-only IOC, and clean up orphaned orders. Write actions are Execution Trader only, on an approved ticket. Use for leverage changes, closes, protection checks and margin questions.
- hyperliquid-setup
Prepare the desk computer to work with Hyperliquid - install the SDKs, pick testnet or mainnet, verify connectivity, and (only when the user asks) provision a trade-only API wallet through the secure secret store and verify it is approved. Use during desk setup, when moving between research, testnet and mainnet levels, when a key is rotated, or when any Hyperliquid call fails with an environment problem.
- hyperliquid-websocket
Subscribe to live Hyperliquid data over WebSocket from the desk computer - mids, order book, trades, candles, best bid/offer, and per-account fills, order updates and events - with raw JSON, Python SDK and TypeScript examples, plus how to run a supervised watch that logs to a file and alerts. Read-only. Use for monitoring, fill notifications and any watch that polling would make expensive.
Using hypergrok in Claude Code
Ask for an agent by name:
@agent-hypergrok:desk-lead
@agent-hypergrok:execution-traderSkills need no command. Claude reads them when your request matches what they describe.
Update, turn off or remove
- Update the plugin (shell)
- claude plugin update hypergrok@hypergrok
- Refresh the marketplace
- /plugin marketplace update hypergrok
- Turn it off for now
- /plugin disable hypergrok@hypergrok
- Remove it
- /plugin uninstall hypergrok@hypergrok
Skills in hypergrok
- desk-execution-protocolgalleonlabs/hypergrok-trading-desk
The Execution Trader's procedure for turning an approved ticket into one Hyperliquid action and reconciling it - the pre-send checklist, order construction rules, single-send discipline, unknown-result handling and the execution report. Use before and after every send, cancel, modify, leverage change or close.
3 files515stars - desk-incident-responsegalleonlabs/hypergrok-trading-desk
What the desk does when something goes wrong on Hyperliquid - unknown send results, unexpected fills or positions, unprotected positions, stuck or orphaned orders, API outages, rate limiting, and suspected API wallet compromise. Contain first, reconcile from the exchange record, act only through approved tickets, then review. Use the moment anything does not match the ticket.
3 files515stars - desk-monitoringgalleonlabs/hypergrok-trading-desk
How the desk watches markets and the account between trades using Grok Bot routines and WebSocket or polling watches - the desk brief, book checks, funding and price watches, alert conditions and what a watch may and may not do. Use when the user asks for briefings, alerts, "watch X" or scheduled checks.
3 files515stars - desk-operating-modelgalleonlabs/hypergrok-trading-desk
How the HyperGrok trading desk works as a team of Grok Bots - roles, seats, shared workspace, evidence standard, approval model and handoff format. Use when setting up the desk, when a Bot is unsure who owns something, or when a request does not fit the normal trade lifecycle.
3 files515stars - desk-post-trade-reviewgalleonlabs/hypergrok-trading-desk
Enables an agent to journal trading activity, perform post-trade reviews, conduct weekly desk reviews, and document incidents using exchange records.
3 files515stars - desk-risk-limitsgalleonlabs/hypergrok-trading-desk
How the Risk Manager writes the desk's risk limits with the user, sizes every proposed trade from live account state and Hyperliquid's real constraints, checks the book, and issues a PASS or REJECT with exact ticket fields. Use for setting up or changing limits, sizing any trade, and answering "how's the book".
3 files515stars - desk-strategy-labgalleonlabs/hypergrok-trading-desk
How the Strategist works with the user to turn their own trading idea into explicit rules, backtest it honestly on Hyperliquid candle and funding history, and paper-trade it on testnet through the desk lifecycle. Method only - the desk ships no strategies and makes no return claims. Use when the user wants to design, test, compare or paper-trade an idea.
3 files515stars - desk-trade-lifecyclegalleonlabs/hypergrok-trading-desk
The end-to-end procedure for one trade on the HyperGrok desk - from an idea to a reviewed, journaled result - with the ticket format, who owns each stage, and what "done" looks like. Use whenever the user wants to open, adjust or close a position, or whenever any Bot is about to touch the exchange write path.
3 files515stars - hypergrok-bootstrapgalleonlabs/hypergrok-trading-desk
Build and verify a HyperGrok trading desk from the pinned public release. Use for first-run setup, repair, or a readiness check. Starts with a live zero-key Opening Bell, installs the seven role profiles and seventeen shared skills, prepares the Trading Floor, and returns an evidence receipt. Read-only by default; never requests a wallet or places an order.
3 files515stars - hyperliquid-accountgalleonlabs/hypergrok-trading-desk
Read Hyperliquid account data including positions, margin, spot balances, open orders, fills, and portfolio history using curl or Python.
3 files515stars - hyperliquid-advancedgalleonlabs/hypergrok-trading-desk
Less common Hyperliquid actions and their rules - dead-man's switch (scheduleCancel), TWAP orders, spot orders, expiresAfter and nonces, API wallet approval from code, sub-account and vault addressing, HIP-3 dexs, and what the desk deliberately does not do (transfers, withdrawals, builder fees, staking). Write actions are Execution Trader only, on an approved ticket. Use when a ticket asks for one of these or when a user asks whether the desk can.
3 files515stars - hyperliquid-api-referencegalleonlabs/hypergrok-trading-desk
Compact reference for the Hyperliquid API as the desk uses it - endpoints and envelopes, desk-used /info request types and /exchange actions with their signing schemes, order and status vocabularies, asset ids, tick and lot rules, rate limits, WebSocket subscription list, error strings, and where the official docs are. Use to look up an exact field, request type or limit before writing a call, and to map an error string to its cause.
3 files515stars - hyperliquid-market-datagalleonlabs/hypergrok-trading-desk
Read live Hyperliquid market data from the desk computer with curl or the Python SDK - mid, mark and oracle prices, order book depth, funding (current, predicted, historical), open interest, volume, candles, perp and spot metadata, margin tiers, and how to save datasets for the strategy lab. Read-only, no key. Use for any market brief, depth read, funding question or data pull.
3 files515stars - hyperliquid-ordersgalleonlabs/hypergrok-trading-desk
Place, cancel and modify Hyperliquid orders correctly from the desk computer - limit and IOC (market-style) orders, take-profit and stop-loss trigger orders with grouping, client order ids, reduce-only, batch actions, price and size rounding, and how to read every response status. Write path - Execution Trader only, on an approved ticket. Use for any order action and for reconciling by cloid.
3 files515stars - hyperliquid-positionsgalleonlabs/hypergrok-trading-desk
Manage Hyperliquid perp positions and margin from the desk computer - read positions and margin, set leverage and cross/isolated mode, add isolated margin, understand margin tiers and liquidation price, close a position with a reduce-only IOC, and clean up orphaned orders. Write actions are Execution Trader only, on an approved ticket. Use for leverage changes, closes, protection checks and margin questions.
3 files515stars - hyperliquid-setupgalleonlabs/hypergrok-trading-desk
Prepare the desk computer to work with Hyperliquid - install the SDKs, pick testnet or mainnet, verify connectivity, and (only when the user asks) provision a trade-only API wallet through the secure secret store and verify it is approved. Use during desk setup, when moving between research, testnet and mainnet levels, when a key is rotated, or when any Hyperliquid call fails with an environment problem.
3 files515stars - hyperliquid-websocketgalleonlabs/hypergrok-trading-desk
Subscribe to live Hyperliquid data over WebSocket from the desk computer - mids, order book, trades, candles, best bid/offer, and per-account fills, order updates and events - with raw JSON, Python SDK and TypeScript examples, plus how to run a supervised watch that logs to a file and alerts. Read-only. Use for monitoring, fill notifications and any watch that polling would make expensive.
3 files515stars
hypergrok plugin questions
How do I install the hypergrok plugin?
In Claude Code run /plugin marketplace add galleonlabs/hypergrok-trading-desk, then /plugin install hypergrok@hypergrok.
What does the hypergrok plugin include?
hypergrok bundles 7 agents, 17 skills.
Which agents come with hypergrok?
desk-lead, execution-trader, market-analyst, research-analyst, risk-manager, strategist +1. Call one with @agent-hypergrok:desk-lead.
How do I update or remove the hypergrok plugin?
Update it with claude plugin update hypergrok@hypergrok in your shell, or from the Installed tab of /plugin. Remove it with /plugin uninstall hypergrok@hypergrok.
What license is the hypergrok plugin under?
MIT, as stated in the plugin's manifest.