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/shailesh17/mcp-httpserver-proxy/agents-mdgit clone --depth 1 https://github.com/shailesh17/mcp-httpserver-proxyWhat 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.00861 | $0.00861 |
| Opus 5 | $0.00430 | $0.00430 |
| Sonnet 5 | $0.00172 | $0.00172 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
mcp-httpserver-proxy 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 yesterday.
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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guidelines for mcp-httpserver-proxy
Welcome, AI agent! This document details the technical architecture, development workflows, strict constraints, coding standards, and Pull Request procedures for this repository.
🎯 Repository Overview
mcp-httpserver-proxy is a transparent bridge between:
- An MCP Client communicating over
stdio(StdioServerTransportfrom@modelcontextprotocol/sdk). - An MCP HTTP Server communicating over Server-Sent Events (
SSEClientTransportfrom@modelcontextprotocol/sdk).
The primary entry point is src/index.ts, which compiles to dist/index.js as an executable Node.js CLI.
⚠️ Critical Constraints & Rules
1. Standard Output (stdout) is Sacred
[!IMPORTANT] NEVER use
console.log()or write arbitrary text toprocess.stdout! The client (Claude Desktop, Cursor, etc.) parsesstdoutstrictly as JSON-RPC Model Context Protocol messages. Any non-protocol output onstdoutwill corrupt the transport and crash the client session.All logging, informational messages, and diagnostics MUST be routed to
process.stderrviaconsole.error().
2. Transport Lifecycle Order
- The proxy must establish and confirm the SSE backend connection (
sseTransport.start()) before startingstdioTransport.start(). - If the SSE backend fails or closes, the proxy must gracefully exit or signal failure without leaving orphaned stdio loops.
- Handle process termination signals (
SIGINT,SIGTERM) to clean up open transport connections.
3. Package Management & Tooling
- Always use
pnpmas the package manager (pnpm install,pnpm run build,pnpm run format,pnpm run check). - Never introduce
npmoryarnlockfiles. - Standard formatting and linting is managed by Trunk:
- Format:
pnpm run format(trunk fmt) - Lint/Check:
pnpm run check(trunk check)
- Format:
4. Git & Commit Standards
- All commit messages and PR titles must follow Conventional Commits:
- Format:
<type>(<scope>): <description> - Types:
feat,fix,docs,style,refactor,perf,test,build,ci,chore,revert.
- Format:
- Commits are verified locally via Trunk git hooks (
commitlint). - PR titles are verified in CI via GitHub Actions (
semantic-pr.yml).
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.
- yesterday First seen · 89 lines · 861 tokens per session scan A 246aa32582af
mcp-httpserver-proxy AGENTS.md is an instructions file published in the GitHub repository shailesh17/mcp-httpserver-proxy (2 stars, last pushed 9d ago), licensed MIT. It adds 861 tokens to every session, about $0.0043 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
mcpm.sh CLAUDE.md
Instructions for pathintegral-institute/mcpm.sh: This file contains conventions that Claude should follow when working on this project.
mcpm.sh GEMINI.md
Instructions for pathintegral-institute/mcpm.sh: Reference CLAUDE.md for project conventions.
Basecamp-MCP-Server CLAUDE.md
Instructions for georgeantonopoulos/Basecamp-MCP-Server, covering claude.md, development commands, setup (one-time) - requires python 3.10+, option 2: using pip (if python 3.10+ already installed) and oauth authentication.
ls-mcp AGENTS.md
Instructions for lirantal/ls-mcp, covering agents.md, start here, documentation, prs and issues and releases.
brightspace-mcp-server AGENTS.md
Instructions for RohanMuppa/brightspace-mcp-server, covering project rules, when adding a new feature, commit format, npm publishing and architecture.
cosmos-mcp CLAUDE.md
Instructions for teampolarity/cosmos-mcp, covering cosmos-mcp, layout, tools (authoritative list in src/tools/index.ts), cli subcommands and imessage is the headline source.