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 commands/echoingvesper/mcp-task-orchestrator/meta-prp-creategit clone --depth 1 https://github.com/EchoingVesper/mcp-task-orchestratorWrote 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/commands/echoingvesper/mcp-task-orchestrator/meta-prp-create)<a href="https://agentmods.dev/commands/echoingvesper/mcp-task-orchestrator/meta-prp-create"><img src="https://agentmods.dev/badge/commands/echoingvesper/mcp-task-orchestrator/meta-prp-create.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 | $0.00000 | $0.05019 |
| Opus 5 | $0.00000 | $0.02509 |
| Sonnet 5 | $0.00000 | $0.01004 |
| Haiku 4.5 | $0.00000 | $0.00502 |
Grade A, and why
meta-prp-create 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 — 571 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create META-PRP with Orchestrator Multi-Agent Coordination
Create comprehensive meta-PRPs that coordinate complex multi-step plans using the task orchestrator's full orchestration capabilities with sub-agent coordination, git worktree isolation, and executive dysfunction design principles.
Meta-PRP Concept: $ARGUMENTS
Template Reference
CRITICAL: Refer to PRPs/templates/meta_prp_structure.md for the complete hierarchical structure template with
executive dysfunction design patterns and git worktree strategy.
Pre-Execution Orchestrator Health Check
MANDATORY FIRST STEP:
# Verify orchestrator connection and full functionality
claude mcp list | grep task-orchestrator || (echo "ORCHESTRATOR NOT CONNECTED - Fixing..." && claude mcp restart task-orchestrator)
# Test orchestrator health before meta-coordination
# This is critical for multi-agent workflows
If orchestrator fails, STOP and spawn fix agent per CLAUDE.md protocol.
Enhanced Context References
CRITICAL: Load and reference these enhanced AI documentation files:
required_context:
- file: PRPs/v2.0-release-meta-prp/meta-coordination-orchestrator.md
why: "Meta-PRP coordination patterns and orchestrator integration examples"
sections: ["Orchestrator Tools Integration", "Phase Structure", "Testing Matrix"]
- file: PRPs/ai_docs/context-engineering-guide.md
why: "Context engineering for multi-agent coordination"
sections: ["Multi-Agent Patterns", "Orchestrator Integration"]
- file: PRPs/ai_docs/mcp-protocol-patterns.md
why: "MCP server coordination and task management patterns"
sections: ["Task Orchestration", "Specialist Assignment"]
- file: PRPs/ai_docs/systematic-testing-framework.md
why: "Multi-agent testing and validation frameworks"
sections: ["Orchestrator Testing", "Complex Workflow Validation"]
- file: CLAUDE.md
why: "Project-specific orchestrator integration requirements"
sections: ["Task Orchestrator Failure Protocol", "Clean Architecture"]
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 · 571 lines · 0 tokens per session scan A 3928908586ba
meta-prp-create is a command published in the GitHub repository EchoingVesper/mcp-task-orchestrator (28 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,019 tokens. 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 commands, from other repositories
workpm
PM 모드로 오케스트레이터 시작. 팀을 구성하고 5단계 워크플로우로 작업을 완수합니다.
proyecto
Declara el proyecto activo (scope global) para atribucion de coste/horas en agentactions. Sin argumento, muestra el proyecto actual.
argos
설계 산출물 대비 구현 검증 — 준공검사 감리 (아르고스).
handover
Works for you. Go outside and live. — AI orchestrator that auto-routes tasks to the cheapest model that solves them. 70% run free on local models. Self-auditing, self-improving, zero prompting skill needed. Built with vibe coding by a finance student. Your models, your data.
instinct-status
Shows learned instincts from dqiii8.db, grouped by project and confidence. Internal diagnostic tool — not for user invocation.
test-team
Works for you. Go outside and live. — AI orchestrator that auto-routes tasks to the cheapest model that solves them. 70% run free on local models. Self-auditing, self-improving, zero prompting skill needed. Built with vibe coding by a finance student. Your models, your data.