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/code-yeongyu/cc-plus/pr-creatornpx skills add code-yeongyu/cc-plus --skill pr-creatorgit clone --depth 1 https://github.com/code-yeongyu/cc-plusWhat 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.00051 | $0.02216 |
| Opus 5 | $0.00026 | $0.01108 |
| Sonnet 5 | $0.00010 | $0.00443 |
| Haiku 4.5 | $0.00005 | $0.00222 |
Grade A, and why
pr-creator 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 2d 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Creator
Workflow for creating GitHub Pull Requests. Analyzes changes, writes clear PRs matching the user's query language, and creates them via gh CLI after user confirmation.
Language Policy: Always match the user's query language. If the user writes in Korean, write the PR in Korean. If the user writes in English, write the PR in English.
Workflow
0. Create TODO list for tracking
CRITICAL: ALWAYS start by creating a TODO list using TodoWrite tool.
Create todos for all workflow steps:
{
"todos": [
{"content": "Gather git status", "status": "pending", "activeForm": "Gathering git status"},
{"content": "Analyze changes deeply", "status": "pending", "activeForm": "Analyzing changes deeply"},
{"content": "Extract or ask for ticket ID", "status": "pending", "activeForm": "Extracting or asking for ticket ID"},
{"content": "Write PR title", "status": "pending", "activeForm": "Writing PR title"},
{"content": "Detect PR template", "status": "pending", "activeForm": "Detecting PR template"},
{"content": "Write PR body", "status": "pending", "activeForm": "Writing PR body"},
{"content": "Save PR draft and get user confirmation", "status": "pending", "activeForm": "Saving PR draft and getting user confirmation"},
{"content": "Create PR via gh CLI", "status": "pending", "activeForm": "Creating PR via gh CLI"}
]
}
Update each todo's status to "in_progress" when starting that step, and "completed" when finished.
1. Gather git status
Run the parallel git status script to gather all repository information:
python scripts/get_git_status.py
This script executes these commands in parallel using asyncio:
git status- current branch and changesgit diff- unstaged changesgit diff --staged- staged changesgit log --oneline -10- recent commit historygit branch --show-current- current branch name
The script returns JSON output with all results. Parse this to understand the current state.
What ships with it
2 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.
- 2d ago First seen · 286 lines · 51 tokens per session scan A 47ffdbb6ee48
pr-creator is a skill published in the GitHub repository code-yeongyu/cc-plus (4 stars, last pushed 10mo ago), licensed MIT. It adds 51 tokens to every session and 2,216 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…