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/create-prgit clone --depth 1 https://github.com/EchoingVesper/mcp-task-orchestratorWhat 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.01568 |
| Opus 5 | $0.00000 | $0.00784 |
| Sonnet 5 | $0.00000 | $0.00314 |
| Haiku 4.5 | $0.00000 | $0.00157 |
Grade A, and why
create-pr 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 2d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request with Context Engineering
Create a well-structured pull request with proper description, context engineering validation, and security considerations.
PR Title (if provided)
$ARGUMENTS
Pre-Execution Orchestrator Check
MANDATORY FIRST STEP:
# Verify orchestrator connection and health
claude mcp list | grep task-orchestrator || (echo "ORCHESTRATOR NOT CONNECTED - Fixing..." && claude mcp restart task-orchestrator)
# Check orchestrator health before proceeding
# Use orchestrator_health_check if available
If orchestrator fails, STOP and spawn fix agent per CLAUDE.md protocol.
Enhanced Context References
Load and reference project-specific documentation:
required_context:
- file: CLAUDE.md
why: "Project-specific git workflow and commit requirements"
sections: ["Commands", "Critical Directives"]
- file: PRPs/ai_docs/cc_github_actions.md
why: "GitHub integration patterns and workflows"
sections: ["PR Best Practices", "CI Integration"]
- file: PRPs/ai_docs/security-patterns.md
why: "Security considerations for code changes"
sections: ["Secure Development", "Code Review Security"]
Security Considerations
Before creating PR, ensure:
- No secrets or keys committed to repository
- Security-sensitive changes properly reviewed
- Input validation for any new endpoints
- Dependencies security-scanned if updated
- Error handling doesn't leak sensitive information
Process
-
Prepare Branch
# Check current branch git branch --show-current # Ensure we're not on main # If on main, create a feature branch -
Review Changes
# See what will be included git status git diff main...HEAD -
Enhanced Code Quality & Security Validation
# Project-specific code formatting and linting black mcp_task_orchestrator/ isort mcp_task_orchestrator/ # Security scanning bandit -r mcp_task_orchestrator/ || echo "Security issues found - review required" safety check || echo "Dependency security issues found - review required" # Run project tests pytest -v # Type checking if configured mypy mcp_task_orchestrator/ || echo "Type checking not configured or failed"
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.
- 2d ago First seen · 214 lines · 0 tokens per session scan A 8ef8ba978643
create-pr 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,568 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
evolve
Agrupa instincts consolidados en skills accionables y las registra en skills-registry/custom/evolved/. Las skills quedan PENDIENTEREVISION hasta que el usuario las apruebe.
proyecto
Declara el proyecto activo (scope global) para atribucion de coste/horas en agentactions. Sin argumento, muestra el proyecto actual.
svsi-review
/svsi-review {slug} # modo interactivo en sesión Claude Code /svsi-review --batch {file} # delega a predrivereview.py (tmux, no en sesión) /svsi-review --stats # métricas acumuladas desde SQLite.
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.
quality-gate
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.