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 agentmods add skills/hg-pyun/claude-code-marketplace/github-prnpx skills add hg-pyun/claude-code-marketplace --skill github-prgit clone --depth 1 https://github.com/hg-pyun/claude-code-marketplaceWrote 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.svg" alt="Measured on agentmods" 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 | $0.00208 | $0.02611 |
| Opus 5 | $0.00104 | $0.01306 |
| Sonnet 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 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.
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.
- 4d 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 2mo ago), licensed MIT. It adds 208 tokens to every session and 2,611 once invoked, about $0.0010 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…