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.
npx skills add motlin/claude-code-plugins --skill create-pull-requestgit clone --depth 1 https://github.com/motlin/claude-code-pluginsWrote 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/skills/motlin/claude-code-plugins/create-pull-request)<a href="https://agentmods.dev/skills/motlin/claude-code-plugins/create-pull-request"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/create-pull-request/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/skills/motlin/claude-code-plugins/create-pull-request"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/create-pull-request.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.00379 |
| Opus 5.5 | $0.00012 | $0.00152 |
| Sonnet 5.5 | $0.00006 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
create-pull-request 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 9d 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 Pull Request
Use the code:cli, git:git-workflow, and git:commit skills when available. Only create a PR when the user has explicitly asked for one.
Confirm the Branch Is on Upstream Main
git fetch "${UPSTREAM_REMOTE:-upstream}"
git merge-base --is-ancestor "${UPSTREAM_REMOTE:-upstream}/${UPSTREAM_BRANCH:-main}" HEAD
A non-zero exit means the branch is behind. Offer to rebase with the git:git-rebase skill rather than opening a stale PR.
Title
Count the commits the branch adds with git rev-list --count "${UPSTREAM_REMOTE:-upstream}/${UPSTREAM_BRANCH:-main}..HEAD".
- One commit: the title is that commit's message. Never type it from memory; read it from git in a subshell,
"$(git log -1 --pretty=%s)", so it matches exactly. - More than one: write a one-line summary in commit message style.
Create the PR
Always pass an explicit empty body so gh doesn't prompt or auto-fill. When a browser is available, use --web to open the prefilled page for final review. On a headless system, drop --web.
For a single-commit branch, read the title from git:
gh pr create --web --title "$(git log -1 --pretty=%s)" --body ""
For a multi-commit branch, pass the summary title you wrote:
gh pr create --web --title "Summary of the branch in commit message style" --body ""
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.
- 9d ago Changed · +2 lines 0966cc1be4f8
- 22d ago Changed · -21 lines b8cc4811b3aa
- 1mo ago Changed f3fdf95b6cb1
- 1mo ago First seen · 60 lines · 29 tokens per session scan A 21c40e0dbe58
create-pull-request is a skill published in the GitHub repository motlin/claude-code-plugins (20 stars, last pushed yesterday), licensed Apache-2.0. It adds 29 tokens to every session and 379 once invoked, about $0.0001 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 skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.