Borrowing it
Nothing to install: this file belongs to rjwalters/kicad-tools. 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/rjwalters/kicad-tools/main/.claude/commands/loom/champion-pr-merge.mdgit clone --depth 1 https://github.com/rjwalters/kicad-toolsWrote 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/rjwalters/kicad-tools/champion-pr-merge)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/champion-pr-merge"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/champion-pr-merge/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/rjwalters/kicad-tools/champion-pr-merge"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/champion-pr-merge.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.00000 | $0.48714 |
| Opus 5 | $0.00000 | $0.24357 |
| Sonnet 5 | $0.00000 | $0.09743 |
| Haiku 4.5 | $0.00000 | $0.04871 |
Grade A, and why
champion-pr-merge 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 yesterday.
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 — 3,338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Champion: PR Auto-Merge Context
This file contains PR auto-merge instructions for the Champion role. Read this file when Priority 1 work is found (PRs with loom:pr label).
Overview
Auto-merge Judge-approved PRs that are safe, routine, and low-risk.
The Champion acts as the final step in the PR pipeline, merging PRs that have passed Judge review and meet all safety criteria.
⚠️ --body @path Does NOT Expand — It Posts the Literal String
If you post a comment via gh issue comment / gh pr comment / gh api ... comments from a scratch file, --body @path (and gh api -f body=@path)
posts the literal string @path, not the file's contents. Full pitfall,
incident citation, and fixes:
comment-body-literal-path.md.
Cached forge reads (gh-cached, #4667)
Champion runs on a 10-minute cron alongside concurrent Judges and sweeps, all
sharing one personal gh rate-limit budget (#4665). Its repeated
observation reads — idempotency-marker comment greps, backlog scans,
duplicate searches — go through the short-TTL cache wrapper. Its
merge-gating reads do not: this skill performs the single most irreversible
action in the pipeline, so every read a merge decision rests on must observe
current state unconditionally.
Resolve the wrapper once, at the start of the pass:
# Degrades to plain `gh` when absent or when its Python runtime is broken —
# the same probe merge-pr.sh uses. Nothing here depends on the cache existing.
GH_READ="gh"
_ghc="$(git rev-parse --show-toplevel 2>/dev/null)/.loom/scripts/gh-cached"
if [[ -x "$_ghc" ]] && "$_ghc" --version >/dev/null 2>&1; then GH_READ="$_ghc"; fi
Route through $GH_READ (cached, 30s TTL):
- Idempotency-marker comment greps (
--json commentsreads for the verdict-janitor, hold, stale-PR, park, close, and prior-grant markers). These only answer "did I already post this?"; the cache is invalidated by your own--clear-cacheafter you post (see below). - The
loom:blockedunblock scan (gh issue list --label "loom:blocked") and its per-issue body/state reads. - The follow-on-issue duplicate search (
gh issue list --search …). - The parked-PR listing (
gh pr list --label …).
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.
- yesterday Changed · +20 lines dd6d0ebec3a1
- 2d ago Changed · +7 lines 84964bd0de00
- 11d ago First seen · 3,311 lines · 0 tokens per session scan A 0fc64188a967
champion-pr-merge is a command published in the GitHub repository rjwalters/kicad-tools (56 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 48,714 tokens. 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-30.
Other commands, from other repositories
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.
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.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
handoff
Export a Waybill Bundle by default, or import one when requested.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.