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/sandsaber/agentspawnmcp/agents-mdgit clone --depth 1 https://github.com/sandsaber/AgentSpawnMCPWrote 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/sandsaber/agentspawnmcp/agents-md)<a href="https://agentmods.dev/instructions/sandsaber/agentspawnmcp/agents-md"><img src="https://agentmods.dev/badge/instructions/sandsaber/agentspawnmcp/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.1 | $0.02292 | $0.02292 |
| Opus 5 | $0.01146 | $0.01146 |
| Sonnet 5 | $0.00458 | $0.00458 |
| Haiku 4.5 | $0.00229 | $0.00229 |
Grade A, and why
AgentSpawnMCP 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 5d 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentSpawnMCP - Developer Guide
AgentSpawnMCP is a universal MCP server for OpenAI-compatible and
Anthropic-compatible LLM HTTP APIs. It is built on FastMCP and plain httpx.
Do not add provider SDKs unless the project explicitly changes direction.
The core design goal is provider portability: new providers should usually be configuration, CLI arguments, or small request-shape changes, not new client stacks.
Operating Modes
1. Spawn Agents MCP server (recommended integration path)
Runs from an installed package or directly through uvx. It exposes one
provider-specific agent tool plus agent_info.
uvx agent-spawn-mcp spawn \
--name minimax \
--url https://api.minimax.io/anthropic/v1 \
--token-env MINIMAX_TOKEN \
--model MiniMax-M2.7 \
--api-type anthropic
Use this mode for Claude Code, OpenCode, Codex MCP, and other MCP clients when the user only needs to delegate tasks to a single external model/provider.
2. Full MCP server
Runs from a cloned checkout and registers the full tool set: chat, stateful chat, vision, files, search, image generation, provider info, and agent tools.
git clone https://github.com/sandsaber/AgentSpawnMCP
cd AgentSpawnMCP
uv sync
uv run python main.py main --provider grok
Use this mode when the user needs the configured provider catalog and the general-purpose MCP tools.
Repository Map
main.py # Thin CLI shim to agent_spawn_mcp.__main__:app
agent_spawn_mcp/__main__.py # Typer CLI: main and spawn commands
agent_spawn_mcp/server.py # create_server() for the full server
agent_spawn_mcp/utils.py # Local chat history helpers
agent_spawn_mcp/config/models.py # Pydantic config models and BUILTIN_PROVIDERS
agent_spawn_mcp/config/loader.py # load_config(), active provider globals
agent_spawn_mcp/providers/base.py # Base provider shape
agent_spawn_mcp/providers/openai_compat.py # HTTP client for OpenAI/Anthropic-style APIs
agent_spawn_mcp/tools/ # Full server MCP tool registration modules
agent_spawn_mcp/agent_spawn/server.py # create_agent_spawn_server()
agent_spawn_mcp/agent_spawn/tools/base.py # _create_agent_tool() factory
agent_spawn_mcp/agent_spawn/tools/registry.py
configs/default.yaml # Default full-server provider catalog
tests/ # Request-shape and URL-construction tests
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.
- 5d ago First seen · 277 lines · 2,292 tokens per session scan A c48674830d20
AgentSpawnMCP AGENTS.md is an instructions file published in the GitHub repository sandsaber/AgentSpawnMCP (0 stars, last pushed 3mo ago), licensed MIT. It adds 2,292 tokens to every session, about $0.0115 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
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.
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.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).