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/prp-spec-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/prp-spec-create)<a href="https://agentmods.dev/commands/echoingvesper/mcp-task-orchestrator/prp-spec-create"><img src="https://agentmods.dev/badge/commands/echoingvesper/mcp-task-orchestrator/prp-spec-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.01969 |
| Opus 5 | $0.00000 | $0.00984 |
| Sonnet 5 | $0.00000 | $0.00394 |
| Haiku 4.5 | $0.00000 | $0.00197 |
Grade A, and why
prp-spec-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 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create SPEC PRP with Context Engineering
Generate a comprehensive specification-driven PRP with clear transformation goals using enhanced context engineering principles and security-first design.
Specification: $ARGUMENTS
Pre-Execution Orchestrator Check
MANDATORY FIRST STEP:
# Verify orchestrator connection
claude mcp list | grep task-orchestrator || (echo "ORCHESTRATOR NOT CONNECTED - Fixing..." && claude mcp restart task-orchestrator)
# Initialize orchestrator session for specification PRP development
# Use orchestrator_initialize_session with working_directory
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/ai_docs/context-engineering-guide.md
why: "Systematic context engineering for specification-driven development"
sections: ["Context Engineering Framework", "Specification Patterns"]
- file: PRPs/ai_docs/mcp-protocol-patterns.md
why: "MCP server implementation patterns for specification compliance"
sections: ["Core Principles", "State Management"]
- file: PRPs/ai_docs/systematic-testing-framework.md
why: "Testing framework for specification validation"
sections: ["Specification Testing", "Validation Patterns"]
- file: PRPs/ai_docs/security-patterns.md
why: "Security-first design for specification changes"
sections: ["Secure Refactoring", "State Security"]
- file: CLAUDE.md
why: "Project-specific architecture and specification constraints"
sections: ["Clean Architecture", "Architecture Layers"]
Security Considerations
All specification PRPs must include:
- Security impact assessment of proposed changes
- Data flow security validation
- State transition security analysis
- Backward compatibility security implications
- Migration security considerations
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 · 285 lines · 0 tokens per session scan A 5871315bdc4a
prp-spec-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 1,969 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.