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/gzupark/claude-plugin-pack/pr-workflownpx skills add GzuPark/claude-plugin-pack --skill pr-workflowgit clone --depth 1 https://github.com/GzuPark/claude-plugin-packWrote 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/gzupark/claude-plugin-pack/pr-workflow)<a href="https://agentmods.dev/skills/gzupark/claude-plugin-pack/pr-workflow"><img src="https://agentmods.dev/badge/skills/gzupark/claude-plugin-pack/pr-workflow.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.00039 | $0.01757 |
| Opus 5 | $0.00019 | $0.00879 |
| Sonnet 5 | $0.00008 | $0.00351 |
| Haiku 4.5 | $0.00004 | $0.00176 |
Grade A, and why
pr-workflow 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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Workflow
Create GitHub Pull Requests with automated change analysis and code review.
Triggers
- User runs
/pror/pr [base-branch] - User asks to create a PR or pull request
- User wants to push changes and create a PR
- User requests code review before PR creation
Workflow Overview
Step 1: Pre-checks -> Step 2: Detect Base Branch -> Step 3: Verify Changes
-> Step 4: Check Existing PR -> Step 5: Gather Context
-> Step 6: Code Review -> Step 7: Push Confirmation
-> Step 8: Generate PR -> Step 9: Complete
Step 1: Pre-checks
Stop immediately if any check fails.
1.1 Verify Git Repository
git rev-parse --is-inside-work-tree
Fail: "Not a git repository."
1.2 Check Current Branch
git branch --show-current
Fail (empty): "Cannot determine current branch. You are in detached HEAD state."
1.3 Check Uncommitted Changes
git status --porcelain
Fail (any output): "There are uncommitted changes. Run /commit first."
1.4 Verify gh CLI
gh --version
Fail: "gh CLI is not installed. Install it from https://cli.github.com"
1.5 Verify gh Authentication
gh auth status
Fail: "GitHub authentication required. Run gh auth login first."
Step 2: Detect Base Branch
If no base branch provided:
- Try:
git remote show origin | grep 'HEAD branch' | cut -d: -f2 | tr -d ' ' - Fallback to
mainif exists - Fallback to
masterif exists - Fail: "Cannot find default branch. Please specify base branch explicitly."
Step 3: Verify Changes Exist
git diff <base-branch>...HEAD --stat
Fail (no output): "No difference from base-branch."
Step 4: Check Existing PR
gh pr list --head $(git branch --show-current) --json url --jq '.[0].url'
If URL returned: "A PR already exists for this branch: [URL]"
Step 5: Gather Context
Collect information for review and PR generation:
# Commit history
git log <base-branch>..HEAD --oneline
# Changed files summary
git diff <base-branch>...HEAD --stat
# Full diff for review
git diff <base-branch>...HEAD
What ships with it
3 files 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 · 280 lines · 39 tokens per session scan A c78dc50f33ab
pr-workflow is a skill published in the GitHub repository GzuPark/claude-plugin-pack (6 stars, last pushed 7mo ago), licensed MIT. It adds 39 tokens to every session and 1,757 once invoked, about $0.0002 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…