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 agents/ibm/mcp-context-forge/autogengit 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.00000 | $0.00335 |
| Opus 5 | $0.00000 | $0.00168 |
| Sonnet 5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
autogen 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.
r = requests.post(f"{GATEWAY}/rpc", json=payload, headers=headers, timeout=30) What it actually says
AutoGen Integration with ContextForge
AutoGen is an open-source framework from Microsoft for building multi-agent systems. It supports tool calling and dynamic agent coordination.
🔧 MCP Support
Experimental support for MCP integration is available via custom ToolAgent wrappers that call MCP tools via HTTP or mcpgateway-wrapper.
Minimal example using HTTP JSON-RPC with requests:
import os
import requests
GATEWAY = os.getenv("GATEWAY", "http://localhost:4444")
TOKEN = os.getenv("MCPGATEWAY_BEARER_TOKEN")
def call_tool(name: str, arguments: dict):
payload = {
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {"name": name, "arguments": arguments},
}
headers = {"Authorization": f"Bearer {TOKEN}", "Content-Type": "application/json"}
r = requests.post(f"{GATEWAY}/rpc", json=payload, headers=headers, timeout=30)
r.raise_for_status()
return r.json()
# Example usage inside an AutoGen tool wrapper
result = call_tool("get_system_time", {"timezone": "Europe/Dublin"})
print(result)
For stdio-based integration, launch mcpgateway-wrapper and connect AutoGen via a subprocess bridge.
🔗 Resources
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 · 45 lines · 0 tokens per session scan A 354daee9ad5c
autogen is an agent published in the GitHub repository IBM/mcp-context-forge (4,399 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 335 tokens. 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 agents, from other repositories
ai-readiness-reporter
Runs the AgentRC readiness assessment on the current repository and produces a self-contained, static HTML dashboard at reports/index.html. Explains every readiness pillar, the maturity level, and an actionable remediation plan, framed by AgentRC measure → generate → maintain loop. Use when asked to assess, audit…
Custom Agent Foundry
Expert at designing and creating VS Code custom agents with optimal configurations.
Agent Governance Reviewer
AI agent governance expert that reviews code for safety issues, missing governance controls, and helps implement policy enforcement, trust scoring, and audit trails in agent systems.
chat-agents
Build AI-powered chat interfaces with AIChatAgent and useAgentChat. Messages are automatically persisted to SQLite, streams resume on disconnect, and tool calls work across server and client.
webhooks
Receive webhook events from external services and route them to dedicated agent instances. Each webhook source (repository, customer, device) can have its own agent with isolated state, persistent storage, and real-time client connections.
retries
Retry failed operations with exponential backoff and jitter. The Agents SDK provides built-in retry support for scheduled tasks, queued tasks, and a general-purpose this.retry() method for your own code.