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.
git clone --depth 1 https://github.com/hiromaily/go-crypto-walletWrote 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/hiromaily/go-crypto-wallet/recreate-pr)<a href="https://agentmods.dev/commands/hiromaily/go-crypto-wallet/recreate-pr"><img src="https://agentmods.dev/badge/commands/hiromaily/go-crypto-wallet/recreate-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/hiromaily/go-crypto-wallet/recreate-pr"><img src="https://agentmods.dev/badge/commands/hiromaily/go-crypto-wallet/recreate-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.00860 |
| Opus 5.5 | $0.00000 | $0.00344 |
| Sonnet 5.5 | $0.00000 | $0.00172 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
recreate-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.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recreate PR #{pr_number}
Create a copy of an existing PR with review comments summarized as fixes. This allows Gemini (or other reviewers) to re-review the changes.
Purpose
- Copy an existing PR to get a fresh review
- Consolidate all commits into one
- Summarize review comments as actionable fixes in the new PR description
Process
Step 1: Fetch Original PR Information
# Get PR details (title, body, branch)
gh pr view {pr_number} --json title,body,headRefName,baseRefName,files
# Get review comments
gh api repos/{owner}/{repo}/pulls/{pr_number}/comments
# Get PR reviews
gh api repos/{owner}/{repo}/pulls/{pr_number}/reviews
# Get PR diff
gh pr diff {pr_number}
Step 2: Checkout Original Branch and Create New Branch
# Fetch the original PR branch
gh pr checkout {pr_number}
# Get the original branch name
ORIGINAL_BRANCH=$(git branch --show-current)
# Switch to main and update
git checkout main
git fetch origin
git reset --hard origin/main
# Create new branch with -v2 suffix
NEW_BRANCH="${ORIGINAL_BRANCH}-v2"
git checkout -b ${NEW_BRANCH}
Step 3: Apply Changes as Single Commit
Option A: Cherry-pick and squash (if original has multiple commits)
# Get commits from original PR
gh pr view {pr_number} --json commits
# Cherry-pick all commits
git cherry-pick <commit1> <commit2> ...
# Squash into single commit
git reset --soft HEAD~N # N = number of commits
git commit -m "squashed commit message"
Option B: Apply diff directly
# Apply the PR diff to the new branch
gh pr diff {pr_number} | git apply
# Commit all changes
git add -A
git commit -m "consolidated changes from PR #{pr_number}"
Step 4: Analyze Review Comments
Extract and categorize review comments:
| Category | Action |
|---|---|
| Bug/Error | Must fix |
| Improvement | Should address |
| Style/Naming | Apply convention |
| Question | Document or clarify |
Step 5: Create New PR
Create PR with original message + review summary:
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 · 165 lines · 0 tokens per session scan A 46baca24808b
recreate-pr is a command published in the GitHub repository hiromaily/go-crypto-wallet (128 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 860 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-09-01.
Other commands, from other repositories
elegant-code-review
Review the current working diff against the elegant-code decision ladder and propose deletions, honoring the negligence floor.
prp-commit
Quick commit with natural language file targeting: describe what to commit in plain English.
gsd:pr-branch
Create a clean PR branch by filtering out .planning/ commits — ready for code review.
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.
karpathy-check
Revisa as alterações em stage (ou o último commit) com base nos 4 princípios de codificação do Karpathy. Verifica complexidade, ruído no diff, suposições ocultas e verificação de objetivos. Uso: /karpathy-check [--last-commit].
review
Review code against project rules using the code-reviewer agent.