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/xt.net/copilot-instructionsgit clone --depth 1 https://github.com/JKorf/XT.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/xt.net/copilot-instructions)<a href="https://agentmods.dev/instructions/jkorf/xt.net/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jkorf/xt.net/copilot-instructions.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.00806 | $0.00806 |
| Opus 5 | $0.00403 | $0.00403 |
| Sonnet 5 | $0.00161 | $0.00161 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
XT.Net copilot-instructions.md 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 3d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions for XT.Net
This repository is XT.Net, a strongly typed C#/.NET client library for the XT cryptocurrency exchange API. It is part of the CryptoExchange.Net ecosystem.
When generating code that consumes XT.Net, follow these conventions.
Use XT.Net, not raw HTTP
Never generate HttpClient calls to XT endpoints. Always use XTRestClient or XTSocketClient so signing, rate limiting, serialization, and error handling are handled by the library.
Client Setup
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, credentials are not required: new XTRestClient().
Result Handling
Methods return WebCallResult<T> or WebCallResult for REST and CallResult<T> for WebSocket subscriptions. Always check .Success before reading .Data. The error is on .Error.
API Structure
restClient.SpotApi.ExchangeData- spot market datarestClient.SpotApi.Account- spot balances, deposits, withdrawals, transfers, websocket tokenrestClient.SpotApi.Trading- spot orders and user tradesrestClient.UsdtFuturesApi.*- USDT-M futures RESTrestClient.CoinFuturesApi.*- Coin-M futures RESTsocketClient.SpotApi- spot WebSocket streamssocketClient.FuturesApi- futures WebSocket streams
Private spot socket streams require restClient.SpotApi.Account.GetWebsocketTokenAsync(). Private futures socket streams require restClient.UsdtFuturesApi.Account.GetListenKeyAsync() or the matching futures REST account listen key.
Order Placement
Spot orders require TimeInForce and BusinessType:
var order = await restClient.SpotApi.Trading.PlaceOrderAsync(
"eth_usdt", OrderSide.Buy, OrderType.Limit,
TimeInForce.GoodTillCanceled, BusinessType.Spot,
quantity: 0.01m, price: 2000m);
Futures orders require PositionSide:
var order = await restClient.UsdtFuturesApi.Trading.PlaceOrderAsync(
"ETH_USDT", OrderSide.Buy, OrderType.Market, 0.01m, PositionSide.Long);
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.
- 3d ago First seen · 82 lines · 806 tokens per session scan A 6ec9b39be1fb
XT.Net copilot-instructions.md is an instructions file published in the GitHub repository JKorf/XT.Net (5 stars, last pushed 6d ago), licensed MIT. It adds 806 tokens to every session, about $0.0040 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
WhiteBit.Net copilot-instructions.md
Instructions for JKorf/WhiteBit.Net, covering copilot instructions for whitebit.net, use whitebit.net, not raw http, client setup, result handling and api structure.
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.
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…
HyperLiquid.Net copilot-instructions.md
Instructions for JKorf/HyperLiquid.Net, covering copilot instructions for hyperliquid.net, use hyperliquid.net, not raw http, client setup, result handling and api structure.
toobit-net
Use Toobit.Net when generating C#/.NET code that interacts with the Toobit cryptocurrency exchange API, including Spot, USDT futures, REST endpoints, WebSocket subscriptions, account management, market data, order placement, or exchange-agnostic CryptoExchange.Net SharedApis code.