Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add dwmkerr/claude-toolkit/plugin install toolkitWrote 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/dwmkerr/claude-toolkit/ghpr)<a href="https://agentmods.dev/commands/dwmkerr/claude-toolkit/ghpr"><img src="https://agentmods.dev/badge/commands/dwmkerr/claude-toolkit/ghpr/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/dwmkerr/claude-toolkit/ghpr"><img src="https://agentmods.dev/badge/commands/dwmkerr/claude-toolkit/ghpr.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.00010 | $0.00533 |
| Opus 5.5 | $0.00004 | $0.00213 |
| Sonnet 5.5 | $0.00002 | $0.00107 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
ghpr 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
GitHub Pull Request
Open or create a pull request for the current branch.
Context
- Current branch: !
git branch --show-current - Recent commits on this branch: !
git log main..HEAD --oneline 2>/dev/null || git log origin/main..HEAD --oneline 2>/dev/null || echo "Unable to determine commits"
Instructions
Step 1: Check if PR exists (fast path)
Run the ghpr script:
${CLAUDE_PLUGIN_ROOT}/scripts/ghpr.sh
- If it shows "✔ opened: ": The PR was opened in the browser. Confirm this to the user and stop.
- If it shows "NO_PR": Continue to Step 2.
Step 2: Check for relevant skills
Before creating a PR, check available skills for any that might provide PR guidance:
- Look for
<project>-developmentskills (e.g.,ark-development,typescript-development) if this is engineering work - Look for
pull-requestorpr-guidanceskills - Review the conversation history for context about what was implemented
If relevant skills exist, invoke them to get project-specific PR conventions.
Step 3: Create PR (if none exists)
a. Analyze the branch name and commits to determine the type:
feat/branch or feature commits →feat:fix/branch or bugfix commits →fix:chore/branch or maintenance commits →chore:docs/branch →docs:refactor/branch →refactor:
b. Draft a PR title following conventional commit format (e.g., feat: add ghpr command)
c. Draft a PR body using this format:
## Summary
- Brief description of changes
d. Present the suggested title and body to the user using AskUserQuestion:
- Show the proposed title
- Show the proposed body
- Ask for confirmation or edits
e. If confirmed, create the PR:
gh pr create --title "..." --body "..."
f. Report the PR URL to the user.
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 · 65 lines · 10 tokens per session scan A 98cfa46d4651
ghpr is a command published in the GitHub repository dwmkerr/claude-toolkit (23 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 533 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
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
land
Resolve and squash merge one named, currently authorized pull request.
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
github-modes
This document describes all GitHub integration modes available in Claude-Flow with ruv-swarm coordination. Each mode is optimized for specific GitHub workflows and includes batch tool integration for maximum efficiency.
ship
Deliver one goal end to end (clarify, implement, PR, review, CI, merge) via the ship skill.
gsd:ship
Create PR, run review, and prepare for merge after verification passes.