agentmods.dev

create-pr

create-pr is a skill for Claude Code, Codex, Cursor from ymhhh/cursor-implements. It costs 57 tokens per session (483 once invoked), scanned A, original, MIT.

A procedure for creating a GitHub pull request with the gh command-line tool. It checks the branch and changes, prepares a summary and test plan, pushes the branch when needed, and opens the request.

In plain words
What is it for?
Preparing and opening a GitHub pull request from the current branch, including reviewing commits, drafting the title and description, pushing the branch, and recording tests and risks.
Why use it?
It turns completed branch work into a reviewable pull request with consistent information about changes, testing, risks, and rollback. It also checks conditions such as uncommitted work and branch safety.

Skill for Claude CodeCodexCursor

not rated 2 27d ago A scan 57 tokens original MIT
View the source file ymhhh/cursor-implements
Install

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.

agentmods
npx agentmods add skills/ymhhh/cursor-implements/create-pr
Any agent
npx skills add ymhhh/cursor-implements --skill create-pr
Clone the repo
git clone --depth 1 https://github.com/ymhhh/cursor-implements

Made for: Claude Code, Codex, Cursor.

Wrote 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.

agentmods badge for create-pr

README.md
[![agentmods](https://agentmods.dev/badge/skills/ymhhh/cursor-implements/create-pr.svg)](https://agentmods.dev/skills/ymhhh/cursor-implements/create-pr)
Your own site
<a href="https://agentmods.dev/skills/ymhhh/cursor-implements/create-pr"><img src="https://agentmods.dev/badge/skills/ymhhh/cursor-implements/create-pr.svg" alt="Measured on agentmods" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 483 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00057 $0.00483
Opus 5 $0.00028 $0.00242
Sonnet 5 $0.00011 $0.00097
Haiku 4.5 $0.00006 $0.00048

Measured 4d ago against content hash 4a7854b85d7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 4d 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.

.cursor/skills/create-pr/SKILL.md · 60 lines

What it actually says

Create Pull Request (gh)

Overview

Turn current branch work into a PR using gh pr create, with summary/test plan/risks/rollback aligned to pr-author and IMPLEMENTATION_PLAN.md.

Preconditions

  • gh authenticated for the repo remote
  • Branch is not bare main/master unless the user explicitly wants that
  • Do not update git config; do not force-push to main/master

Workflow

  1. Gather state in parallel:
    • git status
    • git diff and git diff --staged
    • git log --oneline (and vs base: git log origin/main...HEAD or default branch)
    • git rev-parse --abbrev-ref HEAD / upstream tracking
  2. If there are uncommitted changes the user intended to include: stop and ask to commit first (or run git-commit skill).
  3. Analyze all commits that will be in the PR (not only the latest).
  4. Draft title + body (pr-author structure):
    • Summary (1–3 bullets)
    • Test plan (checklist)
    • Risks / Rollback
    • Link acceptance criteria from IMPLEMENTATION_PLAN.md when present
  5. Push if needed: git push -u origin HEAD (request network/all permissions as required).
  6. Create PR:
gh pr create --title "the pr title" --body "$(cat <<'EOF'
## Summary
- …

## Test plan
- [ ] …

## Risks / Rollback
- …

EOF
)"
  1. Return the PR URL.

Notes

  • Prefer the repo’s default base branch (gh repo view --json defaultBranchRef).
  • If pr-author was already used in-session, reuse that draft rather than rewriting from scratch.
  • Do not open a PR with empty commits / no diff vs base.
Changes

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.

  1. 4d ago First seen · 60 lines · 57 tokens per session scan A 4a7854b85d7c

Subscribe to this mod's changes

create-pr is a skill published in the GitHub repository ymhhh/cursor-implements (2 stars, last pushed 27d ago), licensed MIT. It adds 57 tokens to every session and 483 once invoked, about $0.0003 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-31.

Git and workflow
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens