Borrowing it
Nothing to install: this file belongs to go-to-k/cdkd. 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/go-to-k/cdkd/main/.claude/skills/create-pr/SKILL.mdgit clone --depth 1 https://github.com/go-to-k/cdkdWrote 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/go-to-k/cdkd/create-pr)<a href="https://agentmods.dev/skills/go-to-k/cdkd/create-pr"><img src="https://agentmods.dev/badge/skills/go-to-k/cdkd/create-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/skills/go-to-k/cdkd/create-pr"><img src="https://agentmods.dev/badge/skills/go-to-k/cdkd/create-pr.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.00031 | $0.00932 |
| Opus 5.5 | $0.00012 | $0.00373 |
| Sonnet 5.5 | $0.00006 | $0.00186 |
| Haiku 4.5 | $0.00003 | $0.00093 |
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 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PR
Run all quality checks and create a GitHub PR if everything passes.
Steps
-
Ensure on a feature branch with the right cwd:
git branch --show-current— check current branch- Multi-worktree pre-flight: if the current branch is
main(ormaster), also rungit worktree list --porcelainand check whether any other worktree is on a non-main branch. If yes, surface that explicitly:
The user almost certainly meant to rungit worktree list --porcelain | awk '/^worktree /{wt=$2} /^branch refs\/heads\//{b=substr($0,index($0,"refs/heads/")+11); if (b!="main" && b!="master") print wt " on branch " b}'/create-prfrom that worktree — every latergit/gh pr viewcall defaults to cwd, so running from the parent worktree onmainreports "no PR found for branch 'main'" while a feature branch with commits sits elsewhere. Stop and ask whether to proceed in the listed worktree (offercd <path>) before falling through to "create a new branch". - If on
mainand no other worktrees have non-main branches, ask the user for a branch name and create it:git checkout -b <branch-name>. - Branch naming convention:
feat/,fix/,refactor/,docs/,chore/prefix. - Later steps assume cwd is that worktree; if the user defers the cd, abort rather than guess.
-
Run
/verify-pr— typecheck, lint, build, tests, CI, docs consistency, leftover resources. If any check fails, stop and report. -
Ensure changes are committed and pushed:
git status— commit any uncommitted changes that belong to this branch's workgit push -u origin <branch>— ensure remote is up to date
-
Check if PR already exists for the current branch:
gh pr view --json number,url -q '.url' 2>/dev/null- If a PR exists, update its title/body (see /verify-pr step 12), report the URL, and stop — skip steps 5–8
-
Gather PR context:
git log main...HEAD --oneline— all commits in this branchgit diff main...HEAD --stat— changed files summary- Determine base branch (default:
main, overridable with--base)
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 Changed 74a0b3a5136b
- 1mo ago Changed c40841b3a4e0
- 1mo ago Changed 3507efe86c22
- 1mo ago Changed 9e5c6ac85ebc
- 2mo ago First seen · 70 lines · 31 tokens per session scan A 49ad00941b5a
create-pr is a skill published in the GitHub repository go-to-k/cdkd (156 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 932 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
prowler-pr
Creates Pull Requests for Prowler following the project template and conventions. Trigger: When working on pull request requirements or creation (PR template sections, PR title Conventional Commits check, changelog gate/no-changelog label), or when inspecting PR-related GitHub workflows like conventional-commit.yml…
aws-cdk-mcp-server-mcp
AWS Cloud Development Kit (CDK) best practices, infrastructure as code patterns, and security compliance with CDK Nag.
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.