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-trade-lifecyclegit 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-trade-lifecycle)<a href="https://agentmods.dev/skills/galleonlabs/hypergrok-trading-desk/desk-trade-lifecycle"><img src="https://agentmods.dev/badge/skills/galleonlabs/hypergrok-trading-desk/desk-trade-lifecycle/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-trade-lifecycle"><img src="https://agentmods.dev/badge/skills/galleonlabs/hypergrok-trading-desk/desk-trade-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 96 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00077 | $0.01774 |
| Opus 5 | $0.00039 | $0.00887 |
| Sonnet 5 | $0.00015 | $0.00355 |
| Haiku 4.5 | $0.00008 | $0.00177 |
Grade A, and why
desk-trade-lifecycle 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 12d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trade lifecycle
Every position change on the desk goes through the same seven stages, in order. Skipping one is a defect, not a shortcut. The Desk Lead keeps the lifecycle moving; the owner of each stage does the work.
idea -> evidence -> risk sign-off -> user approval -> execution -> reconciliation -> review
DL MA/RA RM user ET ET TR
0. Open a proposal
Owner: Desk Lead. As soon as a trade idea appears (from the user, the Strategist, or a routine), assign an id HG-YYYYMMDD-NN (NN increments per day) and create /workspace/trading-desk/proposals/<id>.md:
# HG-20260816-01
- opened: 2026-08-16 14:02 UTC by user
- market: ETH-PERP network: mainnet account: 0xabc...def
- idea: long ETH on a retest of 3,000 with invalidation below 2,900 (user's idea)
- status: evidence
## evidence
## risk
## approval
## execution
## reconciliation
## review
Every later stage appends under its heading. The file is the single record of the trade; chat is context.
1. Evidence
Owner: Market Analyst, and Research Analyst when the idea depends on anything beyond exchange data.
The Desk Lead asks for exactly what sizing and execution will need: current mid, mark and oracle; funding now and predicted; open interest and 24h volume; depth within 5/10/25 bps for the intended size; the market's constraints (max leverage, margin tiers, size decimals, minimum order value); recent range and volatility. Research adds anything scheduled or breaking that touches the market. Both write their blocks under ## evidence with sources and UTC times.
Done when: the Risk Manager has every input it needs and nothing is older than a few minutes.
2. Risk sign-off
Owner: Risk Manager. Reads risk-limits.md, reads live account state, computes size from the user's stop and risk budget, checks every gate, and writes PASS or REJECT with exact ticket fields under ## risk (procedure and arithmetic in desk-risk-limits).
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.
- 12d ago First seen · 117 lines · 77 tokens per session scan A 34c5c89baa61
desk-trade-lifecycle is a skill published in the GitHub repository galleonlabs/hypergrok-trading-desk (60 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 1,774 once invoked, about $0.0004 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.
polymarket
Use when the user wants to trade, research, or backtest Polymarket prediction markets through Superior Trade — finding markets by slug or event URL, placing a single immediate market order, writing NautilusTrader strategies, running filled-data backtests, funding pUSD, or deploying and monitoring a live Polymarket…
backtesting
Use when running, interpreting, or designing backtests on Superior Trade — anything about backtest windows, trade-count thresholds, exit-reason mix, parameter sweeps, walk-forward validation, zero-trade diagnosis, compute-cost estimation, or "is this backtest result trustworthy?". Pair with the relevant strategy…
fees-optimizations
Use when the user asks about fees, fee optimization, slippage, maker vs taker, post-only or ALO orders, fee tiers, builder code fees, effective spread, order pricing, lowering trading costs, or why a live Hyperliquid Freqtrade strategy underperforms its backtest. Also use proactively for high-turnover designs (5m or…
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…