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 hg-pyun/claude-code-marketplace/plugin install dev-toolsWrote 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/hg-pyun/claude-code-marketplace/github-pr)<a href="https://agentmods.dev/skills/hg-pyun/claude-code-marketplace/github-pr"><img src="https://agentmods.dev/badge/skills/hg-pyun/claude-code-marketplace/github-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/hg-pyun/claude-code-marketplace/github-pr"><img src="https://agentmods.dev/badge/skills/hg-pyun/claude-code-marketplace/github-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.00208 | $0.02611 |
| Opus 5.5 | $0.00083 | $0.01044 |
| Sonnet 5.5 | $0.00042 | $0.00522 |
| Haiku 4.5 | $0.00021 | $0.00261 |
Grade A, and why
github-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 2mo 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Use_When>
- User asks to create a PR ("PR 만들어줘", "create a PR")
- User signals ready-for-review ("리뷰 보내줘", "send this for review")
- User invokes
/github-prslash command - Branch has commits the user wants captured in a PR </Use_When>
<Do_Not_Use_When>
- User is reviewing an existing PR (use a review tool or the PR thread)
- User asks PR status questions ("did my PR merge?") — answer directly via
gh pr view - User discusses PR workflow conceptually
- Current branch is the default branch (cannot PR main → main) </Do_Not_Use_When>
<Why_This_Exists>
Writing PR titles + bodies by hand is tedious and inconsistent. This skill drafts a conventional-commit-style title from the commit log, fills in a Summary/Changes body in $LANGUAGE from the diff, and uses GitHub MCP to create or update the PR. Base-branch detection via reflog handles stacked PRs and unusual workflows without forcing the user to specify.
</Why_This_Exists>
<Execution_Policy>
- Use GitHub MCP tools for all GitHub operations (PR lookup/creation/update). Fall back to
ghCLI only if MCP is unavailable. Base-branch detection is git-local first — no network call unless the local paths fail (see Step 2). - PR title
type(scope)parts stay English; the description portion is$LANGUAGE. - PR body section headers (
## Summary,## Changes) stay English; section content is$LANGUAGE. - Issue links (
Closes #123) stay English. - The body must use real newline characters, never escaped
\nliterals. - Automatic reviewer/label assignment is not performed.
- Breaking change
!marker is not automatically added. </Execution_Policy>
<Settings_Reference>
$LANGUAGE: the language setting fromplugin.jsonsettings.language(defaultKorean). Override with--lang=<value>. Presets: Korean, English, Japanese, Chinese. Custom values accepted. </Settings_Reference>
Validate:
- If the current branch is the default branch (main/master), abort with an error.
- If there are uncommitted changes, warn the user but continue.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 180 lines · 208 tokens per session scan A 7a43ad37b702
github-pr is a skill published in the GitHub repository hg-pyun/claude-code-marketplace (2 stars, last pushed 4mo ago), licensed MIT. It adds 208 tokens to every session and 2,611 once invoked, about $0.0008 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-31.
Other skills, from other repositories
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.
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.
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.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…