Borrowing it
Nothing to install: this file belongs to akiojin/llmlb. 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/akiojin/llmlb/develop/.gemini/skills/gwt-pr-check/SKILL.mdgit clone --depth 1 https://github.com/akiojin/llmlbWrote 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/akiojin/llmlb/gwt-pr-check)<a href="https://agentmods.dev/skills/akiojin/llmlb/gwt-pr-check"><img src="https://agentmods.dev/badge/skills/akiojin/llmlb/gwt-pr-check/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/akiojin/llmlb/gwt-pr-check"><img src="https://agentmods.dev/badge/skills/akiojin/llmlb/gwt-pr-check.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.00033 | $0.02815 |
| Opus 5.5 | $0.00013 | $0.01126 |
| Sonnet 5.5 | $0.00007 | $0.00563 |
| Haiku 4.5 | $0.00003 | $0.00281 |
Grade A, and why
gwt-pr-check 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- gh-pr-check — 92% identical, 19 lines differ
How it starts
The opening of the file, as written. The whole thing — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GH PR Check
Overview
Check PR status for the current branch with gh and report a recommended next action.
This skill is check-only:
- Do not create/switch branches
- Do not push
- Do not create/edit PRs
Decision rules (must follow)
- Resolve repository,
headbranch, andbasebranch.head: current branch (git rev-parse --abbrev-ref HEAD)base: defaultdevelopunless user specifies
- Optionally collect local working tree state:
git status --porcelain- Report as context only; do not mutate files.
- Fetch latest remote refs before comparing:
git fetch origin
- List PRs for head branch:
gh pr list --head <head> --state all --jsonnumber,state,mergedAt,updatedAt,url,title,mergeCommit,baseRefName,headRefName
- Classify:
- No PR found ->
NO_PR+ recommended actionCREATE_PR - Any PR where
mergedAt == null->UNMERGED_PR_EXISTS+ recommended actionPUSH_ONLY - All PRs merged -> perform post-merge commit check
- No PR found ->
- Post-merge commit check (critical when all PRs are merged):
- Select latest merged PR by
mergedAt - Get merge commit SHA from
mergeCommit.oid - Verify merge commit ancestry before counting:
git merge-base --is-ancestor <merge_commit> HEAD
- If merge commit is ancestor of
HEAD, count commits after merge:git rev-list --count <merge_commit>..HEAD
- If count > 0 ->
ALL_MERGED_WITH_NEW_COMMITS+CREATE_PR - If count == 0 ->
ALL_MERGED_NO_NEW_COMMITS+NO_ACTION
- Select latest merged PR by
- Fallback when merge commit SHA is missing or not an ancestor of
HEAD:- First compare against branch upstream (preferred):
git rev-list --count origin/<head>..HEAD
- Count > 0 ->
ALL_MERGED_WITH_NEW_COMMITS+CREATE_PR(fallback) - Count == 0 ->
ALL_MERGED_NO_NEW_COMMITS+NO_ACTION(fallback) - If upstream comparison fails, compare against base:
git rev-list --count origin/<base>..HEAD
- If base comparison fails ->
CHECK_FAILED+MANUAL_CHECK
- First compare against branch upstream (preferred):
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 · 339 lines · 33 tokens per session scan A cc22ba3bed48
gwt-pr-check is a skill published in the GitHub repository akiojin/llmlb (10 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 2,815 once invoked, about $0.0001 per session on Opus 5.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-10-21.
Other skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
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.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
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…