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 rules/jkorf/xt.net/xt-netgit clone --depth 1 https://github.com/JKorf/XT.NetWhat 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.00000 | $0.00717 |
| Opus 5 | $0.00000 | $0.00358 |
| Sonnet 5 | $0.00000 | $0.00143 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
xt-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 2d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
XT.Net Conventions
This codebase uses XT.Net for XT cryptocurrency exchange access. Do not write raw HttpClient calls to XT endpoints.
Client Setup Pattern
using XT.Net;
using XT.Net.Clients;
var restClient = new XTRestClient(options =>
{
options.ApiCredentials = new XTCredentials("API_KEY", "API_SECRET");
});
For public market data only, no credentials are needed: new XTRestClient().
Result Pattern
All methods return WebCallResult<T> or WebCallResult for REST and CallResult<T> for WebSocket. Always check .Success before reading .Data.
var ticker = await restClient.SpotApi.ExchangeData.GetTickersAsync("eth_usdt");
if (!ticker.Success) { Console.WriteLine(ticker.Error); return; }
var first = ticker.Data.First();
API Surface
restClient.SpotApi.{ExchangeData|Account|Trading}restClient.UsdtFuturesApi.{ExchangeData|Account|Trading}restClient.CoinFuturesApi.{ExchangeData|Account|Trading}socketClient.SpotApisocketClient.FuturesApi
Do not generate socketClient.UsdtFuturesApi or socketClient.CoinFuturesApi; futures sockets are under FuturesApi.
WebSocket Pattern
var socketClient = new XTSocketClient();
var sub = await socketClient.SpotApi.SubscribeToTickerUpdatesAsync(
"eth_usdt",
update => Console.WriteLine(update.Data.LastPrice));
if (!sub.Success) { Console.WriteLine(sub.Error); return; }
await socketClient.UnsubscribeAsync(sub.Data);
Private spot streams need restClient.SpotApi.Account.GetWebsocketTokenAsync(). Private futures streams need restClient.UsdtFuturesApi.Account.GetListenKeyAsync().
Multi-Exchange Code
For exchange-agnostic code, use CryptoExchange.Net.SharedApis:
using CryptoExchange.Net.SharedApis;
var shared = new XTRestClient().SpotApi.SharedClient;
var ticker = await shared.GetSpotTickerAsync(
new GetTickerRequest(new SharedSymbol(TradingMode.Spot, "BTC", "USDT")));
Hard Rules
- Never write raw
HttpClientXT endpoint calls. - Never use
.Resultor.Wait(); useawait. - Never instantiate clients per request; reuse or use DI.
- Never skip checking
WebCallResult.Success. - Always use
XTCredentials("key", "secret"), not genericApiCredentials. - Always store WebSocket subscriptions and unsubscribe on shutdown.
- Always inspect
XT.Net/Interfaces/Clients/**before generating methods not in the map.
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.
- 2d ago First seen · 89 lines · 0 tokens per session scan A 84f91f85bb08
xt-net is a cursor rule published in the GitHub repository JKorf/XT.Net (5 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 717 tokens. 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 cursor rules, from other repositories
whitebit-net
Conventions for using WhiteBit.Net when working with the WhiteBit cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with WhiteBit APIs.
kraken-net
Conventions for using Kraken.Net when working with Kraken Spot and Futures cryptocurrency exchange APIs in C#/.NET. Apply when generating code that interacts with Kraken API.
toobit-net
Conventions for using Toobit.Net when working with the Toobit cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with the Toobit API.
mexc-net
Conventions for using Mexc.Net library when working with the MEXC cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with the MEXC API.
bingx-net
Conventions for using BingX.Net library when working with the BingX exchange in C#/.NET. Apply when generating code that interacts with the BingX API.
hyperliquid-net
Conventions for using HyperLiquid.Net when working with the HyperLiquid DEX in C#/.NET, including spot, futures, account, HIP-3 DEX, and HIP-4 outcome APIs. Apply when generating code that interacts with the HyperLiquid API.