Borrowing it
Nothing to install: this file belongs to EchoingVesper/mcp-task-orchestrator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/EchoingVesper/mcp-task-orchestrator/main/.claude/commands/development/create-pr.mdgit 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/create-pr)<a href="https://agentmods.dev/commands/echoingvesper/mcp-task-orchestrator/create-pr"><img src="https://agentmods.dev/badge/commands/echoingvesper/mcp-task-orchestrator/create-pr/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/echoingvesper/mcp-task-orchestrator/create-pr"><img src="https://agentmods.dev/badge/commands/echoingvesper/mcp-task-orchestrator/create-pr.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01568 |
| Opus 5.5 | $0.00000 | $0.00627 |
| Sonnet 5.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 2mo 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.
- 2mo 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
review-branch
Review an existing branch holistically before merging — blast radius, conventions, security, and spec compliance.
pr
Open a Pull Request on GitHub following team conventions. Draft by default.
pr-manager
Comprehensive pull request management with ruv-swarm coordination for automated reviews, testing, and merge workflows.
generate-linear-worklog
You are tasked with generating a technical work log comment for a Linear issue based on recent git commits.
add-changelog
Generate and maintain project changelog.
pr-enhance
Command "pr-enhance" from shyftlabs/continuum, covering pr-enhance, usage, options, examples and enhance pr.