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/feelyourprotocol/mcp-gateway/agents-mdgit clone --depth 1 https://github.com/feelyourprotocol/mcp-gatewayWrote 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/feelyourprotocol/mcp-gateway/agents-md)<a href="https://agentmods.dev/instructions/feelyourprotocol/mcp-gateway/agents-md"><img src="https://agentmods.dev/badge/instructions/feelyourprotocol/mcp-gateway/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 | $0.00701 | $0.00701 |
| Opus 5 | $0.00351 | $0.00351 |
| Sonnet 5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
mcp-gateway 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 3d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent notes
Tool-agnostic entrypoint for coding agents working in mcp-gateway.
Read this file first. Then load .cursor/rules/mcp-surface.mdc.
Depends one-way on mcp-execution-engine via LocalTaskProcessor. Human docs: mcp-docs.feelyourprotocol.org.
What this repo is
MCP transport + tool registry. Maps generic MCP tools to engine query shapes. No simulation logic here.
Agent → mcp-gateway (this repo) → mcp-execution-engine → EthereumJS
MCP identity
| Constant | Value | Notes |
|---|---|---|
SERVER_NAME |
FeelYourProtocol |
MCP handshake name — product id, not -EVM (server scope is broader than EVM) |
| Config key (docs) | feel-your-protocol |
User-chosen in mcp.json; kebab-case |
| CLI / logs | fyp-mcp |
Bin and stderr prefix |
Live tools (v0.1)
| MCP tool | Engine call |
|---|---|
describe_capabilities |
describeCapabilities() |
run_evm_bytecode |
simulateBytecode() |
Do not add per-EIP MCP tools (e.g. simulate_eip8024). EIP coverage is advertised via tool descriptions + live probe output.
Repo layout
| Path | Role |
|---|---|
src/tools/ |
MCP tool registration + descriptions |
src/schemas/ |
Zod input shapes (mirror schemas/*.json for docs site) |
src/engine/TaskProcessor.ts |
Seam for worker pool / queue later |
src/index.ts |
stdio entry |
src/http/ |
HTTP transport (planned production) |
Adding or changing a tool
- Implement engine support first (if new query shape)
- Extend
TaskProcessor+LocalTaskProcessor - Add
src/tools/*.ts, register inregisterTools.ts - Add Zod schema + JSON schema copy for mcp-docs
- Update
TOOL_NAMESinsrc/server/constants.ts - Integration tests in
src/__tests__/mcp.integration.spec.ts - Update mcp-docs
use/tools/page
Docs map
| Audience | Where |
|---|---|
| Human MCP users | mcp-docs/use/ |
| Engine internals | mcp-docs/internals/ + mcp-execution-engine/AGENTS.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.
- 3d ago First seen · 66 lines · 701 tokens per session scan A 7d71febee89c
mcp-gateway AGENTS.md is an instructions file published in the GitHub repository feelyourprotocol/mcp-gateway (0 stars, last pushed 3d ago), licensed MIT. It adds 701 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-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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.