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/smart-mcp-proxy/mcpproxy-go/agents-mdgit clone --depth 1 https://github.com/smart-mcp-proxy/mcpproxy-goWhat 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.00772 | $0.00772 |
| Opus 5 | $0.00386 | $0.00386 |
| Sonnet 5 | $0.00154 | $0.00154 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
mcpproxy-go AGENTS.md scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `scripts/verify-api.sh` — exercise the `/api/v1` REST surface with curated curl calls. How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
cmd/mcpproxyhosts the core daemon entrypoint;cmd/mcpproxy-traybuilds the CGO-based tray binary.- Runtime logic, HTTP handlers, storage, and upstream orchestration live in
internal/(internal/runtime,internal/httpapi,internal/upstream,internal/storage). - Vue/Tailwind assets are kept in
frontend/; bundled static output is embedded fromweb/. - Integration and regression assets reside under
tests/andscripts/; Go unit tests sit beside source files.
Build, Test, and Development Commands
make build— compile the proxy and tray binaries for the host platform.go build ./cmd/mcpproxy— quick core rebuild;GOOS=darwin CGO_ENABLED=1 go build ./cmd/mcpproxy-trayvalidates the macOS tray target.npm install && npm run buildinsidefrontend/— install web deps and emit production assets.scripts/run-web-smoke.sh— spin up the proxy and execute the Playwright smoke suite.scripts/verify-api.sh— exercise the/api/v1REST surface with curated curl calls.
Coding Style & Naming Conventions
- Run
gofmt(tabs, goimports defaults) on all Go sources; prefer descriptive package-level names (runtime,upstream,storage). - TypeScript/Vue files follow Prettier defaults (
npm run lint); components usePascalCase.vue, composables useuseThing.ts. - Configuration and DTO structs live in shared packages (
internal/contracts,internal/httpapi); avoid anonymous maps between layers.
Testing Guidelines
- Unit tests:
go test ./internal/...(setGOCACHE/GOMODCACHEto workspace paths when sandboxed). - Targeted suites:
go test ./internal/server -run TestMCP -vfor lifecycle checks;npm run test:unitfor frontend units. - End-to-end:
scripts/run-e2e-tests.shafter ensuring@modelcontextprotocol/server-everythingis warmed and reachable. - Name Go tests
TestFeatureScenario; snapshot or fixture data belong undertests/with explicit prefixes.
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.
- 2d ago First seen · 42 lines · 772 tokens per session scan A ede6b3214f1b
mcpproxy-go AGENTS.md is an instructions file published in the GitHub repository smart-mcp-proxy/mcpproxy-go (326 stars, last pushed 2d ago), licensed MIT. It adds 772 tokens to every session, about $0.0039 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
TitanX AGENTS.md
Instructions for CES-Ltd/TitanX, covering aionui - project guide, code conventions, file & directory structure, naming and ui library & icons.
nomos CLAUDE.md
Instructions for safe-agentic-world/nomos, covering claude.md, commands, architecture, package map and conventions to preserve.
nomos AGENTS.md
Instructions for safe-agentic-world/nomos, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
mcpkernel copilot-instructions.md
Copilot instructions for piyushptiwari1/mcpkernel, covering mcpkernel — project context for all agents, project overview, architecture, code standards and build & test.
mcpkernel testing-guidelines.instructions.md
Use when writing or modifying tests for MCPKernel. Covers pytest patterns, async testing, fixtures, and test structure.
mcpkernel policy-writing.instructions.md
Use when working with MCPKernel YAML policy files. Covers policy syntax, rule structure, OWASP ASI mappings, and best practices for writing security policies.