Borrowing it
Nothing to install: this file belongs to thecombatwombat/replicant-mcp. 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/thecombatwombat/replicant-mcp/master/.claude/commands/create-pr.mdgit clone --depth 1 https://github.com/thecombatwombat/replicant-mcpWrote 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/thecombatwombat/replicant-mcp/create-pr)<a href="https://agentmods.dev/commands/thecombatwombat/replicant-mcp/create-pr"><img src="https://agentmods.dev/badge/commands/thecombatwombat/replicant-mcp/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/thecombatwombat/replicant-mcp/create-pr"><img src="https://agentmods.dev/badge/commands/thecombatwombat/replicant-mcp/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.00011 | $0.00456 |
| Opus 5.5 | $0.00004 | $0.00182 |
| Sonnet 5.5 | $0.00002 | $0.00091 |
| Haiku 4.5 | $0.00001 | $0.00046 |
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 1mo 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.
What it actually says
Create a pull request with built-in quality gates. Follow these steps exactly:
-
Persist plan: Check
.claude/plans/for a plan file relevant to current branch. If found, copy todocs/plans/YYYY-MM-DD-<branch-topic>-design.mdand stage it. -
Beads validation: Run
bd list --status=in_progress. If no issues found, STOP and ask user to create a beads issue before proceeding. -
Graph check: For each in-progress issue, verify it has a parent epic (
bd show <id>). Warn if orphans found. -
Determine base branch: Check
git log --oneline master..HEADto understand commits on this branch. -
Find changed files: Run
git diff --name-only master...HEADto get all files changed vs base branch. -
ADR check: Review
git diff master...HEADfor significant decisions — architectural (new patterns, technology choices, design trade-offs) OR workflow (process changes, enforcement mechanisms, convention changes). If any found, checkDECISIONS.mdfor a corresponding entry. If missing, add the entry before proceeding. -
Run code-simplifier: Use the Task tool to launch the
code-simplifieragent on changed files. -
Run complexity check: Execute
scripts/check-complexity.sh. If violations found, fix them before proceeding. -
Stage and commit: If the simplifier, ADR additions, or violation fixes made changes, stage and commit them:
git add <changed-files> git commit -m "refactor: simplify code and fix complexity violations" -
Push branch:
git push -u origin HEAD -
Create PR: Use
gh pr createwith a descriptive title and body summarizing all commits on the branch.
If complexity violations persist after the fix attempt, report them and stop — do not create the PR.
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.
- 1mo ago First seen · 35 lines · 11 tokens per session scan A 25ee8a48c2e5
create-pr is a command published in the GitHub repository thecombatwombat/replicant-mcp (18 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 456 once invoked, about $0.0000 per session on Opus 5.5. 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
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
factory
Linha de montagem multi-agente (Software Factory) — spec-writer → builder em worktree isolado → 4 revisores paralelos (Security, Code, UI, UX) → approver com gate de risco e dashboard visual.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
release-tag
Create and push a version tag after a release PR has been merged.