create-pr

A pull-request creation command that gathers project guidance, validates the change, and prepares a structured description with security considerations. A pull request is a request to review and merge changes into a shared codebase.

In plain words
What is it for?
Use it to check the project orchestrator, consult documentation about GitHub workflows and security, and create a pull request from a supplied title or description.
Why use it?
It helps turn completed work into a reviewable pull request that follows the project's workflow and records relevant context.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/echoingvesper/mcp-task-orchestrator/create-pr
Clone the repo
git clone --depth 1 https://github.com/EchoingVesper/mcp-task-orchestrator

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,568 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 8ef8ba978643, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.claude/commands/development/create-pr.md · 214 lines

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

  1. Prepare Branch

    # Check current branch
    git branch --show-current
    
    # Ensure we're not on main
    # If on main, create a feature branch
    
  2. Review Changes

    # See what will be included
    git status
    git diff main...HEAD
    
  3. 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"
    

Read the full file on GitHub · 214 lines

Changes

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.

  1. 2d ago First seen · 214 lines · 0 tokens per session scan A 8ef8ba978643

Subscribe to this mod's changes

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.