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/.claude/commands/gwt-pr-check.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/commands/akiojin/llmlb/gwt-pr-check)<a href="https://agentmods.dev/commands/akiojin/llmlb/gwt-pr-check"><img src="https://agentmods.dev/badge/commands/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/commands/akiojin/llmlb/gwt-pr-check"><img src="https://agentmods.dev/badge/commands/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.00017 | $0.00317 |
| Opus 5.5 | $0.00007 | $0.00127 |
| Sonnet 5.5 | $0.00003 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00032 |
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.
What it actually says
GitHub PR Check Command
Use this command to inspect PR status for the current branch with the gh CLI.
Usage
/gwt:gwt-pr-check [optional context]
Steps
- Load
.claude/skills/gwt-pr-check/SKILL.mdand follow the workflow. - Run
python3 ".codex/skills/gwt-pr-check/scripts/check_pr_status.py" --repo ".". - Ensure
gh auth statussucceeds before running PR checks. - When all PRs for the head are merged, validate merge commit ancestry before counting post-merge commits.
- If the merge commit is missing or not an ancestor of
HEAD, compareorigin/<head>..HEADbefore any base-branch fallback. - If both upstream and base comparisons fail, return
MANUAL CHECKinstead of inferringCREATE PR. - Return the human-readable summary from the script:
- Result
- Recommended next step
- Why
- Context and key evidence
- Append JSON only if the user explicitly asks for machine-readable output.
- Do not push or create/edit PRs in this command.
Examples
/gwt:gwt-pr-check
/gwt:gwt-pr-check check current branch after merge
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 · 42 lines · 17 tokens per session scan A 928ac4dbbafb
gwt-pr-check is a command published in the GitHub repository akiojin/llmlb (10 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 317 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 commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.