Borrowing it
Nothing to install: this file belongs to gate/gate-local-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/gate/gate-local-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/gate/gate-local-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/gate/gate-local-mcp/agents-md)<a href="https://agentmods.dev/instructions/gate/gate-local-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/gate/gate-local-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/gate/gate-local-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/gate/gate-local-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.00570 | $0.00570 |
| Opus 5.5 | $0.00228 | $0.00228 |
| Sonnet 5.5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
gate-local-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 2mo 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 — 20 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/ contains the MCP server and tool registrations. src/index.ts is the stdio entrypoint, src/client.ts and src/utils.ts hold shared API logic, and src/tools/ groups Gate API surfaces by domain (spot.ts, futures.ts, wallet.ts, etc.). Tests live in test/, with helpers in test/helpers/ and shared env bootstrapping in test/setup.ts. Build output goes to dist/. Design notes and implementation plans live under docs/.
Build, Test, and Development Commands
Run npm install to sync dependencies. Use npm run build to compile TypeScript into dist/. Use npm run dev to start the MCP server directly from src/index.ts with tsx during development. Use npm start to run the compiled server. Use npm test to execute the Vitest suite. For a manual smoke test, build first and then pipe JSON-RPC requests into node dist/index.js as shown in README.md.
Coding Style & Naming Conventions
This repo uses ESM TypeScript with 2-space indentation, semicolons, and single quotes. Keep filenames lowercase; use underscores only when the external API naming is already established, such as flash_swap.ts. Export clear verb-based registration functions like registerSpotTools. Match Gate API terminology in tool names and keep imports using explicit .js specifiers from TypeScript sources.
Testing Guidelines
Vitest is the test runner. Add tests under test/*.test.ts; follow the existing domain split such as spot.test.ts and futures.test.ts. Prefer integration-style tests through the MCP client helper in test/helpers/mcp-client.ts. Run npm test before opening a PR. No coverage gate is configured yet, but new tools should ship with corresponding tests for success cases and auth-sensitive behavior where applicable.
Commit & Pull Request Guidelines
Follow the Conventional Commits pattern already in history: test: add futures tool integration tests, chore: add .worktrees/ to .gitignore. Keep subjects imperative and scoped by change type (feat, fix, test, chore). PRs should describe the API area touched, list any required environment variables, and include example requests or screenshots only when behavior visible to MCP clients changes.
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.
- 2mo ago First seen · 20 lines · 570 tokens per session scan A 8de8d15120b4
gate-local-mcp AGENTS.md is an instructions file published in the GitHub repository gate/gate-local-mcp (1 stars, last pushed 6mo ago), licensed MIT. It adds 570 tokens to every session, about $0.0023 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.