Borrowing it
Nothing to install: this file belongs to ChunSam/kiwoom-mcp-server. 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/ChunSam/kiwoom-mcp-server/main/.claude/skills/pr-cycle/SKILL.mdgit clone --depth 1 https://github.com/ChunSam/kiwoom-mcp-serverWrote 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/chunsam/kiwoom-mcp-server/pr-cycle)<a href="https://agentmods.dev/skills/chunsam/kiwoom-mcp-server/pr-cycle"><img src="https://agentmods.dev/badge/skills/chunsam/kiwoom-mcp-server/pr-cycle/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/chunsam/kiwoom-mcp-server/pr-cycle"><img src="https://agentmods.dev/badge/skills/chunsam/kiwoom-mcp-server/pr-cycle.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.00056 | $0.00319 |
| Opus 5 | $0.00028 | $0.00160 |
| Sonnet 5 | $0.00011 | $0.00064 |
| Haiku 4.5 | $0.00006 | $0.00032 |
Grade A, and why
pr-cycle 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 8d 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.
What it actually says
pr-cycle
main은 브랜치 보호가 걸려 있다 — 직접 push 불가, PR 필수, 선형 히스토리.
절차
- main에서
git checkout -b <type>/<slug>. - 게이트:
check && typecheck && test && build. 카운트가 어긋나면 손으로 세지 말고npm run check:write. - tool·모드를 늘렸으면 버전 5곳 범프(minor) →
npm install --package-lock-only. - 커밋 제목
type(scope): 한국어 요약, vX.Y.Z. 본문은 무엇이 아니라 왜. gh pr create→gh pr merge --auto --squash.gh pr checks <n> --watch→MERGED확인 → main 동기화 → 브랜치 삭제.
함정
references/gotchas.md를 PR 올리기 전에 읽는다 — --auto 누락, 낡은 원격 ref,
카운트 수기 계산, 스윕 육안 확인, 요청 body 테스트.
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.
- 8d ago First seen · 25 lines · 56 tokens per session scan A 2d8e3fe41d97
pr-cycle is a skill published in the GitHub repository ChunSam/kiwoom-mcp-server (1 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 319 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
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
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.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
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…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.