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/butgo/butgo-specdrive-lab/github-prnpx skills add butgo/butgo-specdrive-lab --skill github-prgit clone --depth 1 https://github.com/butgo/butgo-specdrive-labWrote 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/butgo/butgo-specdrive-lab/github-pr)<a href="https://agentmods.dev/skills/butgo/butgo-specdrive-lab/github-pr"><img src="https://agentmods.dev/badge/skills/butgo/butgo-specdrive-lab/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.00024 | $0.00610 |
| Opus 5 | $0.00012 | $0.00305 |
| Sonnet 5 | $0.00005 | $0.00122 |
| Haiku 4.5 | $0.00002 | $0.00061 |
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 3d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub PR
Use this skill to prepare and optionally create a GitHub pull request safely.
Preferred argument-based invocation:
$git pr
Read First
Run read-only checks first:
- GitHub remote repository
- current branch
git status --short- whether the current branch is the base branch
- whether commits are pushed
- GitHub CLI authentication status
- existing PR for the current branch
- likely base branch
- recent commits and relevant diff
Prefer gh for GitHub state when available.
Stop Conditions
Stop and ask the user what to do if:
- the current branch appears to be the base branch
- there are uncommitted changes that should be committed first
- commits are not pushed
gh auth statusfails- an existing PR already exists for the branch
- the base branch is ambiguous
Output Before Execution
Reply with:
- remote repository
- head branch
- base branch recommendation
- local status summary
- push / commit readiness
- existing PR status
- PR title candidates
- PR body draft
- approval prompt
Keep the output concise. Draft the PR title in English unless the repository convention says otherwise. Draft the PR body in Korean when the current project workflow is Korean.
Include a copyable approval sentence in the approval prompt. Use this shape and fill in the recommended base, head, and title:
승인. base <base-branch>, head <head-branch>, title은 "<pr-title>" 로 PR 생성해줘.
Approval Gate
Do not run gh pr create until the user explicitly approves the PR title, body, base branch, and head branch.
Before execution, show the exact gh pr create command or an equivalent summary.
Execution
After approval:
- Run
gh pr createwith the approved base/head/title/body. - Confirm the generated PR URL.
- Report the result briefly.
- Include a merge guidance note for the user.
Use this shape for the merge guidance:
머지는 GitHub PR 화면에서 직접 확인 후 진행해줘.
1. PR 페이지를 연다: <pr-url>
2. 변경 파일과 설명을 확인한다.
3. 문제가 없으면 GitHub에서 Merge pull request 를 누른다.
4. 필요하면 merge 후 원격 브랜치를 삭제한다.
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.
- 3d ago First seen · 99 lines · 24 tokens per session scan A 8c6ca427644f
github-pr is a skill published in the GitHub repository butgo/butgo-specdrive-lab (1 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 610 once invoked, about $0.0001 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
codex-auth-setup
Install or refresh codex-multi-auth for the official Codex CLI, run first login, and verify account health and routing.
codexu-release
Run this skill from the repository root. Treat the release as a real public publish: verify the current remote state first, keep unrelated user changes out of release commits, and report exactly what was built, pushed, and released.
example
Example fixture skill for scanner regression coverage.
codexu-pr-review
Review codexU pull requests and decide whether they should be merged, changed, split, declined, or kept as a fork based on product positioning, roadmap, privacy, data semantics, native macOS design, architecture, scope, and verification. Use for PR review, mergeability assessment, contribution triage, and feature-fit…
agentflow
AgentFlow workflow skill. Use this skill when the user needs Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code dispatch, deterministic quality gates, adversarial review, per-task cost tracking, and crash-proof pipeline execution…
context-canvas-checkpoint
Maintain an optional session task map and explicit retrievable references in Context Canvas Codex. Use when navigation or long-context offload would materially help with goals, decisions, progress, dependencies, blockers, next steps, exploration summaries, large textual tool results, or selective historical…