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/bingx.net/copilot-instructionsgit clone --depth 1 https://github.com/JKorf/BingX.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/bingx.net/copilot-instructions)<a href="https://agentmods.dev/instructions/jkorf/bingx.net/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jkorf/bingx.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.00698 | $0.00698 |
| Opus 5 | $0.00349 | $0.00349 |
| Sonnet 5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
BingX.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 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions for BingX.Net
This repository is BingX.Net, a strongly typed C#/.NET client library for the BingX REST and WebSocket APIs. It is part of the CryptoExchange.Net ecosystem.
When generating code that consumes BingX.Net, follow these conventions:
Use BingX.Net, not raw HTTP
Never generate HttpClient calls to BingX API URLs. Always use BingXRestClient or BingXSocketClient. This ensures correct request signing, rate limiting, and error handling.
Client setup
using BingX.Net;
using BingX.Net.Clients;
var restClient = new BingXRestClient(options =>
{
options.ApiCredentials = new BingXCredentials("API_KEY", "API_SECRET");
});
For public market data, credentials are not required.
Result handling
Methods return WebCallResult<T> (REST) or CallResult<T> (WebSocket). Always check .Success before reading .Data. The error is on .Error.
API structure
restClient.SpotApi.ExchangeData- public spot market datarestClient.SpotApi.Account- spot balances, transfers, deposits, withdrawalsrestClient.SpotApi.Trading- spot orders and OCOrestClient.PerpetualFuturesApi.ExchangeData- public perpetual futures market datarestClient.PerpetualFuturesApi.Account- futures balances, position mode, leverage, margin moderestClient.PerpetualFuturesApi.Trading- futures orders and positionsrestClient.SubAccountApi- sub-account endpointssocketClient.SpotApi- Spot WebSocket streamssocketClient.PerpetualFuturesApi- Perpetual Futures WebSocket streams
Symbols
BingX uses hyphenated symbols in this library, for example BTC-USDT and ETH-USDT.
Order placement
Let the library auto-generate clientOrderId. Do not pass a custom value unless required for an existing operational flow.
WebSocket pattern
Store the returned UpdateSubscription and unsubscribe on shutdown via socketClient.UnsubscribeAsync(sub.Data).
Cross-exchange
For code that needs to work across multiple exchanges, use CryptoExchange.Net.SharedApis interfaces (ISpotTickerRestClient, ISpotOrderRestClient, etc.) accessed via .SharedClient properties.
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 · 72 lines · 698 tokens per session scan A 34c176a57cdc
BingX.Net copilot-instructions.md is an instructions file published in the GitHub repository JKorf/BingX.Net (21 stars, last pushed today), licensed MIT. It adds 698 tokens to every session, about $0.0035 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-30.
Other instructions, from other repositories
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…
Mexc.Net copilot-instructions.md
Copilot instructions for JKorf/Mexc.Net, covering copilot instructions for mexc.net, use mexc.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.
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.…
whitebit-net
Use WhiteBit.Net when generating C#/.NET code that interacts with the WhiteBit cryptocurrency exchange, including V4 REST endpoints, WebSocket subscriptions, spot trading, collateral/futures trading, balances, deposits, withdrawals, convert, WhiteBit Codes, sub-accounts, and CryptoExchange.Net shared APIs.