Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add galleonlabs/hypergrok-trading-desk --skill desk-execution-protocolgit clone --depth 1 https://github.com/galleonlabs/hypergrok-trading-deskWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/galleonlabs/hypergrok-trading-desk/desk-execution-protocol)<a href="https://agentmods.dev/skills/galleonlabs/hypergrok-trading-desk/desk-execution-protocol"><img src="https://agentmods.dev/badge/skills/galleonlabs/hypergrok-trading-desk/desk-execution-protocol/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/galleonlabs/hypergrok-trading-desk/desk-execution-protocol"><img src="https://agentmods.dev/badge/skills/galleonlabs/hypergrok-trading-desk/desk-execution-protocol.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00065 | $0.01955 |
| Opus 5 | $0.00032 | $0.00978 |
| Sonnet 5 | $0.00013 | $0.00391 |
| Haiku 4.5 | $0.00006 | $0.00196 |
Grade A, and why
desk-execution-protocol scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execution protocol
This is the only skill on the desk that ends with a request to Hyperliquid's /exchange endpoint, and only the Execution Trader uses it. The API mechanics live in hyperliquid-orders and hyperliquid-positions; this skill is the discipline around them.
Inputs
- The proposal file
/workspace/trading-desk/proposals/<id>.mdwith a Risk Manager PASS and exact ticket fields. - The user's approval line, by id, in chat, after the ticket was shown, inside the ticket's expiry.
- The desk computer configured per
hyperliquid-setup:HYPERLIQUID_NETWORK,HYPERLIQUID_ACCOUNT_ADDRESS, and the API wallet key available to scripts from the environment (never printed).
Pre-send checklist
Run every item and write the result under ## execution before sending. Any failure: do not send, name the item, hand back to the Desk Lead.
- Ticket integrity. Id, PASS and approval refer to the same ticket text. If the Desk Lead edited the ticket after the PASS, it goes back to Risk.
- Network.
HYPERLIQUID_NETWORKequals the ticket's network. Mainnet is never assumed. - Account and wallet.
HYPERLIQUID_ACCOUNT_ADDRESSequals the ticket's account. The API wallet still acts for it (a read that requires the agent to be approved, orextraAgentsfor the account, shows the wallet address). If the desk has never sent from this wallet on this network, send a tiny testnet-style rehearsal on testnet first, not on mainnet. - Price still valid. Fresh mid from
allMidsis within the ticket's slippage tolerance of the ticket price. For a stop or take-profit ticket, the trigger price is on the correct side of the current mark. - Formatting. Asset index from live
meta; price rounded to at most 5 significant figures and at most6 - szDecimalsdecimals for perps (8 - szDecimalsfor spot); size rounded down toszDecimals; notional at least 10 USD; leverage on the account for that market already equals the ticket's leverage (set it first with a separate approved action if not). - cloid and expiry. Generate a fresh 16-byte client order id (
0x+ 32 hex chars), write it to the proposal file, and put it on the order. One cloid per order, never reused. SetexpiresAfteron the send, a minute out (hyperliquid-advanced), and write that deadline beside the cloid. The cloid makes a duplicate detectable;expiresAfteris what later makes the original provably dead. A send with neither cannot be cleanly recovered from an unknown result. - One action. Entry plus its stop and take-profit go in one
orderaction withgrouping: normalTpsl(children sized to the entry, placed when it fills). Protection for an existing position is a standalone reduce-only trigger. Anything else in the ticket that is a different action type (leverage change, cancel) is a separate, separately approved step. - Nothing else pending. No other unreconciled send from this desk in the last few minutes. If there is, reconcile it first.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 88 lines · 65 tokens per session scan A 27421a33a629
desk-execution-protocol is a skill published in the GitHub repository galleonlabs/hypergrok-trading-desk (60 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 1,955 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
hyperliquid
Use when backtesting, deploying, checking funding readiness, or debugging a Hyperliquid strategy through Superior Trade Unified API — writing Freqtrade configs and strategy code, running sweeps, checking managed-wallet balances, trading HIP-3 perps, or diagnosing a deployment that will not start or trade.
aerodrome
Use when creating, validating, backtesting, deploying, sizing, or troubleshooting Aerodrome/Base spot trading strategies through the Superior Trade API, especially Freqtrade configs using exchange.name "aerodrome", AERO/USDC or CHECK/USDC pairs, AMM market swaps, wallet/gas balance checks, no-orderbook pricing, or…
basis-arb
Use when the user asks for spot-perp basis trade, basis arbitrage, cash-and-carry, perp discount, or any setup that reads the spot–perp basis as a positioning signal. Long-perp leg only — pure two-leg basis arb requires a paired spot short (or long) which Freqtrade can't run cleanly. The strategy below captures the…
funding-squeeze
Use when writing a strategy that captures short-squeeze setups on Hyperliquid perps — squeeze, short squeeze fuel, negative funding rally, fade the shorts, paid to long. Goes long when funding APR is deeply negative and price is already rising, then exits on funding normalisation or a time stop. Reads squeeze fuel…
bollinger-reverter-4h
Use when writing a symmetric Bollinger-band mean-reversion strategy on the 4h timeframe — BB reverter, range trader, chop strategy, ADX<25 mean reversion, band-fade with a minimalroi ladder. Long-or-short on 2-sigma band touches with RSI confirmation. Validated on BTC/ETH/SOL/DOGE; numbers and the exact ROI ladder are…
dca-weekly
Use when writing, validating, or troubleshooting a recurring scheduled buy strategy (DCA, dollar-cost averaging, weekly buys, daily buys, monthly accumulation, accumulator) on Superior Trade — especially anything that should "buy more of the same pair" on a calendar trigger rather than a price trigger.