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-executegit 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-execute)<a href="https://agentmods.dev/commands/echoingvesper/mcp-task-orchestrator/meta-prp-execute"><img src="https://agentmods.dev/badge/commands/echoingvesper/mcp-task-orchestrator/meta-prp-execute.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.05057 |
| Opus 5 | $0.00000 | $0.02528 |
| Sonnet 5 | $0.00000 | $0.01011 |
| Haiku 4.5 | $0.00000 | $0.00506 |
Grade A, and why
meta-prp-execute 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 4d 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 — 604 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute META-PRP with Orchestrator Multi-Agent Coordination
Execute comprehensive meta-PRPs using the task orchestrator's full orchestration capabilities to coordinate sub-agents through systematic multi-phase workflows with git worktree isolation and executive dysfunction design principles.
Meta-PRP File: $ARGUMENTS
Template Reference
CRITICAL: This execution assumes the meta-PRP was created using PRPs/templates/meta_prp_structure.md template with
hierarchical structure and git worktree strategy.
Immediate Orchestrator Session Activation
MANDATORY FIRST STEPS - Execute in Order:
# 1. Verify orchestrator connection and full functionality
claude mcp list | grep task-orchestrator || (echo "ORCHESTRATOR NOT CONNECTED - Fixing..." && claude mcp restart task-orchestrator)
# 2. Test critical orchestrator tools for meta-coordination
# orchestrator_health_check must be available and functioning
CRITICAL: If orchestrator fails, STOP and follow CLAUDE.md protocol. Meta-PRPs require full orchestrator functionality.
IMMEDIATE SESSION TAKEOVER:
# 3. Initialize orchestrator session for meta-PRP execution coordination
orchestrator_initialize_session:
working_directory: "/current/project/path"
session_name: "meta-prp-execution-{concept}-{timestamp}"
# 4. Orchestrator becomes the primary coordinator for all sub-agent spawning
orchestrator_role: "primary_execution_coordinator"
coordination_mode: "multi_agent_meta_prp_execution"
Enhanced Context Loading
MANDATORY: Load and understand all context before execution:
required_context_loading:
- file: $ARGUMENTS # The meta-PRP file to execute
why: "Complete meta-PRP specification with orchestrator integration"
sections: ["ALL - complete understanding required"]
- file: PRPs/v2.0-release-meta-prp/meta-coordination-orchestrator.md
why: "Reference implementation patterns for meta-coordination"
sections: ["Orchestrator Tools Integration", "Workflow Patterns", "Testing Matrix"]
- file: PRPs/ai_docs/context-engineering-guide.md
why: "Multi-agent context engineering principles"
sections: ["Multi-Agent Coordination", "Context Sharing Patterns"]
- file: PRPs/ai_docs/systematic-testing-framework.md
why: "Multi-agent testing and validation"
sections: ["Complex Workflow Testing", "Orchestrator Validation"]
- file: CLAUDE.md
why: "Critical orchestrator failure protocols and requirements"
sections: ["Task Orchestrator Failure Protocol", "Critical Directives"]
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.
- 4d ago First seen · 604 lines · 0 tokens per session scan A 624f14ae17f4
meta-prp-execute 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,057 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
proyecto
Declara el proyecto activo (scope global) para atribucion de coste/horas en agentactions. Sin argumento, muestra el proyecto actual.
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.
checkpoint
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.
weekly-review
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.