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 agentmods add skills/gigshow/decker-ai/decker-hyperliquidnpx skills add gigshow/decker-ai --skill decker-hyperliquidgit clone --depth 1 https://github.com/gigshow/decker-aiWrote 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/gigshow/decker-ai/decker-hyperliquid)<a href="https://agentmods.dev/skills/gigshow/decker-ai/decker-hyperliquid"><img src="https://agentmods.dev/badge/skills/gigshow/decker-ai/decker-hyperliquid.svg" alt="Measured on agentmods" height="20"></a>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.00068 | $0.01505 |
| Opus 5 | $0.00034 | $0.00753 |
| Sonnet 5 | $0.00014 | $0.00301 |
| Haiku 4.5 | $0.00007 | $0.00151 |
Grade A, and why
decker-hyperliquid 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 5d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decker + Hyperliquid (DEX) 스킬
Goal
Decker를 통해 Hyperliquid DEX에서 시세 조회·주문 실행. 메인 decker 스킬을 확장.
운영 모델 (에이전트 컨텍스트)
- 메인 시세(서비스 기본): Binance 계열. HL은 병행 —
market_data에data_source=hyperliquid로 주기 적재, 사용자exchange_preference=hyperliquid이면 HL 소스 우선. - Watchlist(TradFi/지수·대표주식): HL universe·
allMids에 실제로 노출될 때만 수집·시그널 대상에 자동 포함. 미노출 심볼은 조회 불가·시그널 없을 수 있음 — 사용자에게 "HL에 아직 없을 수 있어요" 수준으로 안내 (내부 API 경로·URL 출력 금지). - 시그널: Funding/bias 기반 시그널은
judgment_signals에source=hyperliquid_market. 좋은 시그널 알림은 사용자 선호 거래소에 맞춰 시세 표시. - 첫 상장 감지: 운영 DB에 watchlist 활성 이벤트 기록·선택적 관리자 Slack (에이전트가 사용자에게 웹훅 노출 금지).
Quick Reference
| 사용자 말 | 액션 | 비고 |
|---|---|---|
| "HL BTC 0.01 매수해줘", "Hyperliquid에서 이더 매수" | order-request exchange_id=hyperliquid | 승인 플로우 |
| "HL 시세", "Hyperliquid BTC 가격", "HL 바이어스", "SP500/골드/오일 시세" | 시세·바이어스 API (아래 참조) | 인증 불필요 |
| "HL 포지션", "Hyperliquid 포지션" | Assistant API | JWT 필요 |
DECKER_API_URL
시세·바이어스 조회 (HL-L2 확장)
HL 시세·펀딩·바이어스 — 인증 불필요. {DECKER_API_URL} = DECKER_API_URL 환경변수 또는 https://api.decker-ai.com
| 용도 | API | 응답 |
|---|---|---|
| 종목별 시세·펀딩·바이어스 | GET {DECKER_API_URL}/api/v1/hyperliquid/market-state?symbol=BTC |
mark_price, funding_rate, bias |
| HL 통합 시장상태 | GET {DECKER_API_URL}/api/v1/judgment/market-status?exchange=hyperliquid |
sources.hyperliquid (bias, symbols) |
- symbol: BTC, ETH, SOL, XRP, DOGE, BNB, SP500, XYZ100, GOLD, OIL, AAPL, NVDA, TSLA, MSFT, AMZN
- exchange 파라미터: binance | hyperliquid | all (생략 시 전체)
주문 (Hyperliquid)
order-request에 exchange_id=hyperliquid 추가:
GET {DECKER_API_URL}/api/v1/link/slack/order-request?slack_user_id={sender_id}&symbol=BTC&side=buy&quantity=0.01&exchange_id=hyperliquid&openclaw_secret={OPENCLAW_SECRET}
- exchange_id=hyperliquid 필수 (Hyperliquid DEX 실행)
- symbol: BTC, ETH 등 (USDT 선물 자동)
- quantity: 계약 수량
전제 조건
- Decker 가입 + Slack 연동
- user_settings.exchange_preference = hyperliquid 또는 order 시 exchange_id 지정
- Hyperliquid 키 연동 (Decker 설정 → 거래소 API 설정)
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.
- 5d ago First seen · 105 lines · 68 tokens per session scan A fd8c526c7ff6
decker-hyperliquid is a skill published in the GitHub repository gigshow/decker-ai (3 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 1,505 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-31.
Other skills, from other repositories
defi-yield
DeFi yield analysis and optimization — lending rates, LP yields, staking returns, yield farming strategies, risk-adjusted yield comparison, and protocol-level sustainability assessment.
token-unlock-treasury
Token unlock schedule analysis and project treasury tracking — vesting cliffs, linear unlocks, team/investor/ecosystem token releases, treasury diversification, and sell pressure forecasting.
crypto-derivatives
Crypto-derivatives strategies — perpetual funding-rate arbitrage, futures term-structure contango/backwardation trading, and option volatility-smile / Greeks analysis.
onchain-analysis
On-chain data analysis — active addresses / whale tracking / TVL / DEX liquidity, interpretation and signal generation using on-chain valuation metrics such as MVRV / NVT / SOPR.
stablecoin-flow
Stablecoin supply and flow analysis — USDT/USDC mint-burn signals, exchange stablecoin reserves, on-chain stablecoin velocity, and capital rotation indicators for crypto market timing.
jesse-strategy-tests
Use when writing or modifying tests for Jesse's backend — especially behavior tied to a strategy (entries/exits, take-profit/stop-loss, position lifecycle hooks, closed-trade metrics). Documents this repo's strategy-driven test pattern: a thin test in tests/testparentstrategy.py that runs singleroutebacktest('Name')…