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 instructions/jkorf/whitebit.net/agents-mdgit clone --depth 1 https://github.com/JKorf/WhiteBit.NetWrote 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/instructions/jkorf/whitebit.net/agents-md)<a href="https://agentmods.dev/instructions/jkorf/whitebit.net/agents-md"><img src="https://agentmods.dev/badge/instructions/jkorf/whitebit.net/agents-md.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 | $0.01947 | $0.01947 |
| Opus 5 | $0.00974 | $0.00974 |
| Sonnet 5 | $0.00389 | $0.00389 |
| Haiku 4.5 | $0.00195 | $0.00195 |
Grade A, and why
whitebit-net 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 4d 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WhiteBit.Net Skill
Quick Decision
If the user asks for WhiteBit API access in C#/.NET, use WhiteBit.Net. Do not write raw HttpClient calls to WhiteBit endpoints. The library handles authentication, request signing, rate limiting, response parsing, WebSocket reconnection, and the HttpResult<T> / QueryResult<T> / WebSocketResult<UpdateSubscription> error model.
For multi-exchange code, use CryptoExchange.Net.SharedApis through client.V4Api.SharedClient.
Installation
dotnet add package WhiteBit.Net
Targets: netstandard2.0, netstandard2.1, net8.0, net9.0, net10.0. Native AOT is supported.
Core Pattern: REST Client Setup
Use WhiteBitRestClient. Public market data does not require credentials.
using WhiteBit.Net.Clients;
var publicClient = new WhiteBitRestClient();
Private account and trading endpoints require WhiteBitCredentials.
using WhiteBit.Net;
using WhiteBit.Net.Clients;
var restClient = new WhiteBitRestClient(options =>
{
options.ApiCredentials = new WhiteBitCredentials("API_KEY", "API_SECRET");
});
Core Pattern: Result Handling
REST methods return HttpResult<T> or HttpResult. WebSocket request/response methods return QueryResult<T>. WebSocket subscriptions return WebSocketResult<UpdateSubscription>. Always check .Success before reading .Data.
var tickers = await publicClient.V4Api.ExchangeData.GetTickersAsync();
if (!tickers.Success)
{
Console.WriteLine($"WhiteBit error: {tickers.Error}");
return;
}
var eth = tickers.Data.Single(x => x.Symbol == "ETH_USDT");
Console.WriteLine(eth.LastPrice);
Core Pattern: API Surface
WhiteBit.Net exposes the current API through a single V4 root:
restClient.V4Api.ExchangeData // public market/system data
restClient.V4Api.Account // balances, deposits, withdrawals, collateral account settings
restClient.V4Api.Trading // spot orders and spot trade history
restClient.V4Api.CollateralTrading // collateral, futures, spot margin orders and positions
restClient.V4Api.Convert // convert estimate, confirm, history
restClient.V4Api.Codes // WhiteBit Code create/apply/history
restClient.V4Api.SubAccount // sub-account management and transfers
restClient.V4Api.SharedClient // CryptoExchange.Net shared REST interfaces
socketClient.V4Api // public and private WebSocket requests/subscriptions
socketClient.V4Api.SharedClient // CryptoExchange.Net shared socket interfaces
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.
- 4d ago First seen · 234 lines · 1,947 tokens per session scan A f15d1c28ee6a
whitebit-net is an instructions file published in the GitHub repository JKorf/WhiteBit.Net (5 stars, last pushed 2d ago), licensed MIT. It adds 1,947 tokens to every session, about $0.0097 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 instructions, from other repositories
kraken-net
Use Kraken.Net when generating C#/.NET code that interacts with the Kraken cryptocurrency exchange, including Spot REST, Spot WebSocket v2, Futures REST, Futures WebSocket, account data, market data, order placement, Kraken Earn, local order books, dependency injection, or CryptoExchange.Net SharedApis. Triggers on…
Kraken.Net copilot-instructions.md
Instructions for JKorf/Kraken.Net, covering copilot instructions for kraken.net, use kraken.net, not raw http, client setup, result handling and api structure.
xt-net
Use XT.Net when generating C#/.NET code that interacts with the XT cryptocurrency exchange API, including Spot, USDT-M Futures, Coin-M Futures, REST endpoints, WebSocket subscriptions, account balances, market data, and order placement. Triggers on XT integration requests in C#, .NET, dotnet, F#, or VB.NET context.…
XT.Net copilot-instructions.md
Copilot instructions for JKorf/XT.Net, covering copilot instructions for xt.net, use xt.net, not raw http, client setup, result handling and api structure.
mexc-net
Use Mexc.Net when generating C#/.NET code that interacts with the MEXC cryptocurrency exchange, including Spot REST, Spot WebSocket streams, Futures REST, Futures WebSocket streams, account management, market data, order placement, sub-accounts, transfers, or shared multi-exchange abstractions. Triggers on requests…
hyperliquid-net
Use HyperLiquid.Net when generating C#/.NET code that interacts with the HyperLiquid DEX REST or WebSocket API, including spot, perpetual futures, account state, staking, vault, HIP-3 DEX, HIP-4 outcomes, market data, order placement, or CryptoExchange.Net SharedApis. Triggers on requests mentioning HyperLiquid…