Borrowing it
Nothing to install: this file belongs to JKorf/Mexc.Net. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JKorf/Mexc.Net/main/AGENTS.mdgit 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/agents-md)<a href="https://agentmods.dev/instructions/jkorf/mexc.net/agents-md"><img src="https://agentmods.dev/badge/instructions/jkorf/mexc.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.1 | $0.02356 | $0.02356 |
| Opus 5 | $0.01178 | $0.01178 |
| Sonnet 5 | $0.00471 | $0.00471 |
| Haiku 4.5 | $0.00236 | $0.00236 |
Grade A, and why
mexc-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 7d 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mexc.Net Skill
Quick Decision
If the user asks for MEXC API access in C#/.NET, use Mexc.Net. Do not write raw HttpClient calls to MEXC endpoints. The library handles authentication, request signing, rate limiting, WebSocket reconnection, result objects, and typed models.
For multi-exchange code, use CryptoExchange.Net.SharedApis through the .SharedClient properties on SpotApi or FuturesApi. Use .SharedClient.Discover() when code needs runtime metadata about implemented shared interfaces and endpoint options.
Installation
dotnet add package JK.Mexc.Net
Targets: netstandard2.0, netstandard2.1, net8.0, net9.0, net10.0. Native AOT supported on compatible .NET targets.
Core Pattern: REST Client Setup
Always create REST clients via MexcRestClient. Configure credentials for private account and trading endpoints.
using Mexc.Net;
using Mexc.Net.Clients;
var restClient = new MexcRestClient(options =>
{
options.ApiCredentials = new MexcCredentials("API_KEY", "API_SECRET");
});
For public market data, credentials are not required:
var publicClient = new MexcRestClient();
Core Pattern: Result Handling
REST methods return HttpResult<T> or HttpResult. WebSocket subscription methods return WebSocketResult<UpdateSubscription>. Shared symbol/cache helper methods can return ExchangeCallResult<T>. Always check .Success before reading .Data.
var ticker = await restClient.SpotApi.ExchangeData.GetTickerAsync("BTCUSDT");
if (!ticker.Success)
{
Console.WriteLine($"Error: {ticker.Error}");
return;
}
Console.WriteLine(ticker.Data.LastPrice);
Core Pattern: API Surface
The actual Mexc.Net client roots are:
restClient.SpotApi.ExchangeData // public spot market data
restClient.SpotApi.Account // balances, deposits, withdrawals, transfers, user stream listen key
restClient.SpotApi.Trading // spot orders and user trades
restClient.SpotApi.SubAccount // sub-account management and transfers
restClient.SpotApi.SharedClient // shared spot REST interfaces
restClient.FuturesApi.ExchangeData // public futures market data
restClient.FuturesApi.Account // futures balances, leverage, position mode, funding, fees
restClient.FuturesApi.Trading // futures orders, positions, trigger/TP-SL/trailing orders
restClient.FuturesApi.SharedClient // shared futures REST 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.
- 7d ago First seen · 291 lines · 2,356 tokens per session scan A 14471a2c4509
mexc-net is an instructions file published in the GitHub repository JKorf/Mexc.Net (23 stars, last pushed 3d ago), licensed MIT. It adds 2,356 tokens to every session, about $0.0118 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.