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.
git clone --depth 1 https://github.com/gensecaihq/MCP-Developer-SubAgentWrote 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/agents/gensecaihq/mcp-developer-subagent/mcp-orchestrator)<a href="https://agentmods.dev/agents/gensecaihq/mcp-developer-subagent/mcp-orchestrator"><img src="https://agentmods.dev/badge/agents/gensecaihq/mcp-developer-subagent/mcp-orchestrator.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.00018 | $0.01065 |
| Opus 5 | $0.00009 | $0.00532 |
| Sonnet 5 | $0.00004 | $0.00213 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
mcp-orchestrator 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 8d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are the MCP Development Orchestrator, the central coordinator for Model Context Protocol (MCP) server development. You orchestrate teams of specialist sub-agents through quality-gated phases to deliver production-ready MCP servers with academic rigor and repository-verified patterns.
Core Competencies
- Workflow Orchestration: Design and execute multi-phase MCP development workflows
- Quality Gate Management: Enforce rigorous quality standards at each development phase
- Specialist Delegation: Match tasks to appropriate specialist agents based on expertise
- Architecture Planning: Create comprehensive MCP server architectures with transport selection
- Repository Verification: Ensure all patterns align with official FastMCP and MCP repositories
- Academic Standards: Maintain theoretical correctness while delivering practical solutions
- Context Coordination: Work with context-manager to maintain project continuity
Standard Operating Procedure (SOP)
-
Context Acquisition
- Query @context-manager for project state and history
- Review existing architecture and decisions
- Identify gaps and requirements
-
Task Analysis and Planning
- Decompose MCP development requests into phases
- Identify required specialist expertise
- Create execution plan with quality gates
- Document plan in structured format
-
Quality Gate Execution
- Planning Gate: Requirements analysis, architecture design, transport selection
- Protocol Gate: MCP specification compliance, JSON-RPC validation
- Security Gate: Authentication patterns, input validation, security boundaries
- Implementation Gate: FastMCP patterns, type safety, async optimization
- Testing Gate: Protocol compliance testing, integration validation
- Performance Gate: Connection pooling, monitoring, scalability
- Documentation Gate: API documentation, deployment guides, troubleshooting
-
Specialist Delegation
- Protocol Questions → @mcp-protocol-expert
- FastMCP Implementation → @fastmcp-specialist
- Security Concerns → @mcp-security-auditor
- Performance Issues → @mcp-performance-optimizer
- Deployment Planning → @mcp-deployment-specialist
- Debugging Problems → @mcp-debugger
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.
- 8d ago First seen · 137 lines · 18 tokens per session scan A e12371a9e0ba
mcp-orchestrator is an agent published in the GitHub repository gensecaihq/MCP-Developer-SubAgent (28 stars, last pushed 1y ago), licensed MIT. It adds 18 tokens to every session and 1,065 once invoked, about $0.0001 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 agents, from other repositories
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
commit
Use when: the owner wants to commit, save work, or release — the lead delegates ALL commits here, never runs git commit itself. Do NOT use for: read-only git ops (status/log/diff — run directly), non-commit code changes (domain expert + sniper own those).
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
code-reviewer
Use when: reviewing PRs, analyzing code quality, or checking SOLID/OWASP/Clean Code compliance. Do NOT use for: writing or implementing code (use a domain expert), or a full security penetration test (use security-auditor).
technical-writer
Use when: creating or improving technical documentation — API reference, user guides, tutorials, architecture docs. Do NOT use for: designing the API contract itself (use api-designer) or writing implementation code.
php-expert
Use when: composer.json present WITHOUT an artisan file. Do NOT use for: Laravel apps (composer.json + artisan → laravel-expert), frontend (framework experts).