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/mexc.net/copilot-instructionsgit clone --depth 1 https://github.com/JKorf/Mexc.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/mexc.net/copilot-instructions)<a href="https://agentmods.dev/instructions/jkorf/mexc.net/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jkorf/mexc.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.1 | $0.00807 | $0.00807 |
| Opus 5 | $0.00404 | $0.00404 |
| Sonnet 5 | $0.00161 | $0.00161 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
Mexc.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 6d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions for Mexc.Net
This repository is Mexc.Net, a strongly typed C#/.NET client library for the MEXC cryptocurrency exchange API. It is part of the CryptoExchange.Net ecosystem.
When generating code that consumes Mexc.Net, follow these conventions:
Use Mexc.Net, Not Raw HTTP
Never generate raw HttpClient calls to MEXC REST or WebSocket endpoints. Always use MexcRestClient or MexcSocketClient. This ensures correct request signing, rate limiting, reconnection, and error handling.
Client Setup
using Mexc.Net;
using Mexc.Net.Clients;
var restClient = new MexcRestClient(options =>
{
options.ApiCredentials = new MexcCredentials("API_KEY", "API_SECRET");
});
For public market data only, no credentials are needed:
var restClient = new MexcRestClient();
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- public spot market datarestClient.SpotApi.Account- balances, deposits, withdrawals, transfers, user stream listen keysrestClient.SpotApi.Trading- spot orders and user tradesrestClient.SpotApi.SubAccount- sub-account managementrestClient.FuturesApi.ExchangeData- public futures market datarestClient.FuturesApi.Account- futures balances, leverage, position mode, feesrestClient.FuturesApi.Trading- futures orders, positions, trigger/TP-SL/trailing orderssocketClient.SpotApi- spot WebSocket streamssocketClient.FuturesApi- futures WebSocket streams
There is no GeneralApi, UsdFuturesApi, or CoinFuturesApi in Mexc.Net.
Symbol Formats
Spot uses compact symbols such as BTCUSDT.
Futures uses underscore symbols such as BTC_USDT.
Order Placement
Let the library omit/generate clientOrderId. Do not pass a custom value unless required for an existing operational flow.
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.
- 6d ago First seen · 79 lines · 807 tokens per session scan A b5ec993fd75c
Mexc.Net copilot-instructions.md is an instructions file published in the GitHub repository JKorf/Mexc.Net (23 stars, last pushed yesterday), licensed MIT. It adds 807 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-30.
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
Copilot instructions for JKorf/Kraken.Net, covering copilot instructions for kraken.net, use kraken.net, not raw http, client setup, result handling and api structure.
bingx-net
Use BingX.Net when generating C#/.NET code that interacts with BingX, including Spot, Perpetual Futures, REST endpoints, WebSocket subscriptions, account management, market data, or order placement. Triggers on BingX integration requests in C#, .NET, dotnet, F#, or VB.NET context.
BingX.Net copilot-instructions.md
Copilot instructions for JKorf/BingX.Net, covering copilot instructions for bingx.net, use bingx.net, not raw http, client setup, result handling and api structure.
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.
binance-net
Use Binance.Net when generating C#/.NET code that interacts with the Binance cryptocurrency exchange — including Spot, Margin, USD-M Futures, COIN-M Futures, Options, sub-accounts, brokerage, REST endpoints, WebSocket subscriptions, account management, market data, or order placement. Triggers on any request…