By aaronwald
Exchange domain knowledge agents for prediction markets and crypto derivatives
Binance exchange: Spot REST+WS APIs, symbol conventions, rate limits, taker volume, geo-blocking. Use when: Binance connector issues, REST Klines for HOLS, WS trade data, symbol resolution, API rate planning. <example>How do I get taker buy volume from Binance Klines?</example> <example>What is the WS endpoint accessible from US IPs?</example>
Kalshi exchange domain knowledge: API structure, product types, fee schedules, market mechanics, regulatory context. Use when: Kalshi API integration questions, understanding Kalshi market mechanics, fee calculation and optimization, order placement strategy, market lifecycle handling, product category analysis, regulatory or compliance considerations, demo vs production environment differences. <example>What is the taker fee for a 50-cent Kalshi contract?</example> <example>How does Kalshi market lifecycle work from active to settled?</example>
Kraken exchange domain knowledge: Spot WS v2 (ord_type, trade data) and Futures WS v1 (perpetuals, funding rates). Use when: Kraken connector issues, funding rate analysis, perpetual/spot contract mechanics, WebSocket message parsing, product symbol resolution, Spot trade data for marketorder_volume. <example>How does Kraken Futures funding rate work for PF_XBTUSD?</example> <example>What is the WebSocket message format for Kraken ticker updates?</example> <example>Does Kraken Spot WS include ord_type on trade messages?</example>
Polymarket exchange domain knowledge: CLOB API, condition/token model, Gamma REST API, sharding, market discovery, UMA resolution. Use when: Polymarket connector issues, market discovery and filtering, token subscription management, Gamma API pagination, condition/token data model, resolution oracle mechanics, category/tag filtering. <example>How does Polymarket's condition/token model work for multi-outcome events?</example> <example>What is the Gamma API pagination pattern for market discovery?</example>
Exchange symbology and identifier conventions: Kalshi tickers, Kraken pairs, Polymarket tokens. Use when: ticker parsing, cross-exchange identifier mapping, understanding ID formats, trade matching by symbol, XBT/BTC normalization, condition_id vs token_id disambiguation, cross-exchange price unit conversion, pair_id anatomy. <example>How do I map a Kalshi KXBTCD ticker to its Kraken PF_XBTUSD equivalent?</example> <example>What is the difference between Polymarket condition_id and token_id?</example>
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Exchange domain knowledge agents for Claude Code. Pure API/protocol knowledge for prediction markets and crypto derivatives — no pipeline or infrastructure coupling.
| Agent | subagent_type | Focus |
|---|---|---|
| Kalshi | shadow:kalshi | CFTC-regulated event contracts, REST/WS API, fees, crypto tickers |
| Kraken | shadow:kraken | Kraken Futures perpetuals, funding rates, WebSocket API |
| Polymarket | shadow:polymarket | CLOB prediction market, Gamma API, token model, sharding |
| Symbology | shadow:symbology | Cross-exchange identifier formats, ticker anatomy |
Add to ~/.claude/settings.json:
{
"enabledPlugins": {
"shadow@shadowagent": true
}
}
Clone this repo to your local machine. Claude Code discovers plugins from repos in your workspace.
Agents are available as shadow:{name} subagent types in Claude Code's Task tool:
Task(subagent_type="shadow:kalshi", prompt="Explain Kalshi fee calculation for a 50c contract")
These agents pair well with pipeline-specific agents (e.g., from dlawskillz) for end-to-end exchange integration work.
npx claudepluginhub aaronwald/shadowagent --plugin shadowCore skills, domain agents (waldstorm + ssmd), and workflow commands
Track crypto futures, options, perpetual swaps with funding rates, open interest, and derivatives market analysis
Agent-first CLI for the Crypto.com Exchange API. Market data by default; live trading opt-in via API keys. Available --services: market (default), trade, account, advanced, margin, staking, funding, fiat. Update args in MCP settings to expand capabilities.
No description provided.
Paper-trade across Kalshi, Polymarket, Alpaca, and Coinbase from a Claude Code session. Onboarding collects API keys; a tiny Node helper handles scan/order/ledger for all rails. v1 is paper-only.
Multi-DEX perpetual futures CLI + MCP server for AI agents — Pacifica (Solana), Hyperliquid (HyperEVM), Lighter (Ethereum), Aster (BNB Chain). Trade, bridge, arb, and manage positions via natural language.
Agent-first CLI for trading crypto, stocks, forex, and derivatives on Kraken. Paper trading by default; live trading opt-in via API keys.