Borrowing it
Nothing to install: this file belongs to nexus-xyz/nexus-exchange-mcp. 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/nexus-xyz/nexus-exchange-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/nexus-xyz/nexus-exchange-mcpWrote 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/nexus-xyz/nexus-exchange-mcp/agents-md)<a href="https://agentmods.dev/instructions/nexus-xyz/nexus-exchange-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/nexus-xyz/nexus-exchange-mcp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/nexus-xyz/nexus-exchange-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/nexus-xyz/nexus-exchange-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.5 | $0.00323 | $0.00323 |
| Sonnet 5.5 | $0.00161 | $0.00161 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
nexus-exchange-mcp AGENTS.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 18d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contributing guide — nexus-exchange-mcp
The Model Context Protocol server exposing the Nexus Exchange API as agent tools.
Merging
- Don't merge a PR without an approving review — CI passing isn't a substitute.
- Don't merge a PR you didn't author without an approving review and the
author's sign-off. Check the author first
(
gh pr view <n> --json author,reviewDecision). - Re-approval isn't needed for follow-up commits to an already-approved PR.
Pull requests
- One concern per PR; link its tracking issue (
ENG-XXXX) in the title. - Respond to review comments before merging.
Checks (before pushing)
- The repo's lint, typecheck, and test scripts all pass — CI enforces these.
- If you changed the tool surface (a tool's name or input schema) or a
binentry, regeneratepublic-api.txtwithscripts/release_gate/public_api.sh --writeand commit it in the same PR.prepublish-surfacefails on any difference, so a removal shows up in the diff a reviewer reads (ENG-18798). A-line is a breaking change: give the PR a!title, because the next release'sprepublish-verdictfails a patch bump for it.
API contract
- The network → host map lives in exactly one file,
src/networks.ts, copied from the spec'sx-nexus-networks. Never interpolate a host from a network name (mainnet isapi.nexus.xyz, notapi.mainnet.nexus.xyz), and never let an unrecognized network fall back to a default — it is treated as real funds. - No hostname for a private stage belongs in this repo — not in source, docs,
tests, commit messages or PR bodies, and neither does the stage taxonomy that
names them. Point
customat them instead (ENG-9823). Illustrate with RFC 2606 reserved names (example.comin docs,example.invalidin tests) and generic labels (dev,example). customis client-side only: it is not a value the API accepts and must never appear inx-nexus-networks, so it is deliberately not inNETWORK_IDSorNETWORKS. Its funds are a tri-state (real | play | unknown) that a caller declares; matchplaypositively in a guard, never!== "real", orunknownfalls through as if it were safe. A tool that cannot be undone declaresfundsGuardand is refused on an undeclared target.- Keep the pinned
nexus-exchange-apiversion in sync when the spec bumps.spec-autobumpopens that PR for you and labels it breaking or not; merging it is a human decision, andspec-drifton that PR is the check that says whether it needs code changes. - New API capabilities should be surfaced as MCP tools so an agent can use them.
- Every tool declares the spec operations it calls in its
opsfield — required by the type, verified against the handler byscripts/check_spec_drift.py, and the sourceendpoints.txtis generated from. Runnpm run spec:driftafter touching a tool, andnpm run spec:drift:writeif the operation set moved. - Coverage is reported in two units and they are not interchangeable: registered
tools (MCP's own axis) and spec operations (comparable with the other SDKs).
Never report the tool count as a coverage figure. See
docs/coverage-unit.md.
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.
- 18d ago Changed · +7 lines · +123 tokens per session fc209ec9bc07
- 1mo ago First seen · 51 lines · 684 tokens per session scan A 234a51f6ca22
nexus-exchange-mcp AGENTS.md is an instructions file published in the GitHub repository nexus-xyz/nexus-exchange-mcp (3 stars, last pushed 5d ago), licensed Apache-2.0. It adds 807 tokens to every session, about $0.0032 per session on Opus 5.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
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.