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/pr-with-review.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/pr-with-review)<a href="https://agentmods.dev/commands/thecombatwombat/replicant-mcp/pr-with-review"><img src="https://agentmods.dev/badge/commands/thecombatwombat/replicant-mcp/pr-with-review/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/pr-with-review"><img src="https://agentmods.dev/badge/commands/thecombatwombat/replicant-mcp/pr-with-review.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.02246 |
| Opus 5 | $0.00005 | $0.01123 |
| Sonnet 5 | $0.00002 | $0.00449 |
| Haiku 4.5 | $0.00001 | $0.00225 |
Grade A, and why
pr-with-review 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 10d 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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Automation with Review Handling
Automate the full pull request lifecycle: create branch, commit, push, create PR, poll for reviews, address Greptile feedback, and merge on human approval.
Arguments
Parse from $ARGUMENTS:
--branch <name>(required): Branch name (must follow project conventions: feature/, fix/, docs/, refactor/, chore/)--title <title>(required): PR title--body <body>(optional): PR description body--commit-message <msg>(optional): Custom commit message (defaults to PR title)
Phase 1: Setup and Validation
-
Parse arguments from
$ARGUMENTS- Extract branch, title, body, commit_message
- If commit_message not provided, use title
- Validate branch follows naming convention (feature/, fix/, docs/, refactor/, chore/)
-
Verify prerequisites
- Check
ghCLI is authenticated:gh auth status - Check there are changes to commit:
git status --porcelain - If no changes, report error and exit
- Check
-
Report plan to user
- Show: branch name, title, files to be committed
- Proceed automatically (this is a background agent)
Phase 2: Roadmap Documentation Check
Before creating the PR, check if changes might complete a roadmap item.
-
Load roadmap mapping (if it exists)
MAPPING_FILE=".github/roadmap-mapping.yml" if [ -f "$MAPPING_FILE" ]; then # File exists, proceed with check else # Skip check, continue to PR creation fi -
Get changed files
CHANGED_FILES=$(git diff --name-only origin/master) -
Match changed files against roadmap patterns
For each mapping entry in the YAML file, check if any changed files match the patterns using glob matching. Track which roadmap items are potentially affected.
-
Check if README was updated
If any roadmap items matched:
- Check if
README.mdis in the changed files - If README changed, check if the diff includes changes to roadmap tables (lines containing
| **or| Plannedor| Future) - If README has appropriate changes, assume documentation is handled
- Check if
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.
- 10d ago First seen · 290 lines · 11 tokens per session scan A 59644cfb86c9
pr-with-review is a command published in the GitHub repository thecombatwombat/replicant-mcp (16 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 2,246 once invoked, about $0.0001 per session on Opus 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
review-diff
Review the current working diff for correctness, security, and reuse.
elegant-code-review
Review the current working diff against the elegant-code decision ladder and propose deletions, honoring the negligence floor.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
prp-commit
Quick commit with natural language file targeting: describe what to commit in plain English.
fix-comments
Address PR review comments by implementing requested changes automatically.
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.