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/ibm/mcp-context-forge/agents-mdgit clone --depth 1 https://github.com/IBM/mcp-context-forgeWhat 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.07788 | $0.07788 |
| Opus 5 | $0.03894 | $0.03894 |
| Sonnet 5 | $0.01558 | $0.01558 |
| Haiku 4.5 | $0.00779 | $0.00779 |
Grade A, and why
mcp-context-forge 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 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.
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.
Copies of this mod
2 near-identical copies found in the catalogue:
- mcp-context-forge AGENTS.md — 89% identical, 35 lines differ
- mcp-context-forge CLAUDE.md — 89% identical, 35 lines differ
How it starts
The opening of the file, as written. The whole thing — 576 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidelines for AI coding assistants working with this repository.
For domain-specific guidance, see subdirectory AGENTS.md files:
tests/AGENTS.md- Testing conventions and workflowsplugins/AGENTS.md- Plugin framework and developmentcharts/AGENTS.md- Helm chart operationsdocs/AGENTS.md- Documentation authoringmcp-servers/AGENTS.md- MCP server implementationcrates/mcp_runtime/DEVELOPING.md- Rust MCP runtime development workflows, command matrix, and validation
Note: The llms/ directory contains guidance for LLMs using ContextForge solution (end-user runtime guidance), not for code agents working on this codebase.
Project Overview
ContextForge is an open source registry and proxy that federates MCP, A2A, and REST/gRPC APIs with centralized governance, discovery, and observability. It federates tools, agents, and APIs, optimizes agent and tool calling, and supports plugins, auth/RBAC, rate-limiting, virtual servers, multi-transport protocols, and an optional Admin UI.
Project Structure
mcpgateway/ # Core FastAPI application
├── main.py # Application entry point
├── config.py # Environment configuration
├── db.py # SQLAlchemy ORM models and session management
├── schemas.py # Pydantic validation schemas
├── services/ # Business logic layer (50+ services)
├── routers/ # HTTP endpoint definitions (19 routers)
├── middleware/ # Cross-cutting concerns (16 middleware)
├── transports/ # Protocol implementations (SSE, WebSocket, stdio, streamable HTTP)
├── plugins/ # Plugin integration (uses cpex external package)
└── alembic/ # Database migrations
tests/ # Test suite (see tests/AGENTS.md)
plugins/ # Plugin implementations (see plugins/AGENTS.md)
plugins_rust/ # Rust plugin implementations for performance-sensitive paths
charts/ # Helm charts (see charts/AGENTS.md)
docs/ # Architecture and usage documentation (see docs/AGENTS.md)
a2a-agents/ # A2A agent implementations (used for testing/examples)
mcp-servers/ # MCP server templates (see mcp-servers/AGENTS.md)
crates/ # Direct Rust crate folders (runtime and wrapper)
llms/ # End-user LLM guidance (not for code agents)
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 · 576 lines · 7,788 tokens per session scan A e3eff78e7da3
mcp-context-forge AGENTS.md is an instructions file published in the GitHub repository IBM/mcp-context-forge (4,399 stars, last pushed today), licensed Apache-2.0. It adds 7,788 tokens to every session, about $0.0389 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-30.
Other instructions, from other repositories
optillm CLAUDE.md
Instructions for algorithmicsuperintelligence/optillm, covering claude.md, project overview, core architecture, main components and development commands.
superglue CLAUDE.md
Claude Code instructions for superglue-ai/superglue, covering claude.md, quick reference, oss vs ee, conventions and after completing a feature.
mcp-gateway CLAUDE.md
Instructions for theognis1002/mcp-gateway, covering mcp gateway - claude development guide, project overview, core purpose, key features and architecture.
langgraph AGENTS.md
AGENTS.md instructions for langchain-ai/langgraph, covering agents instructions, corridor security analysis, libraries and dependency map.
hatch3r CLAUDE.md
Instructions for hatch3r/hatch3r, covering hatch3r — development instructions, architecture, development commands, two-axis pillar framework (2.0.0) and orchestrator self-discipline (bypass protection).
aeon CLAUDE.md
Instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).