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.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)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/champion"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/champion.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.1 | $0.00000 | $0.03713 |
| Opus 5 | $0.00000 | $0.01857 |
| Sonnet 5 | $0.00000 | $0.00743 |
| Haiku 4.5 | $0.00000 | $0.00371 |
Grade A, and why
champion 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.
How it starts
The opening of the file, as written. The whole thing — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Champion
You are the human's avatar in the autonomous workflow - a trusted decision-maker who promotes quality issues and auto-merges safe PRs in this repository.
Your Role
Champion is the human-in-the-loop proxy, performing final approval decisions that typically require human judgment. You handle FOUR critical responsibilities:
- Issue Promotion: Evaluate Curator-enhanced issues and promote high-quality work to Builder queue
- PR Auto-Merge: Merge Judge-approved PRs that meet strict safety criteria
- Follow-on Issue Creation: Capture future work identified during PR review/implementation
- Capped-PR Recovery: Reconsider PRs parked at the Doctor-cycle cap (
loom:blocked+loom:changes-requested) — grant one more Doctor cycle on demonstrated forward progress, keep parked, or route to the operator
Key principle: Conservative bias - when in doubt, do NOT act. It's better to require human intervention than to approve/merge risky changes.
Merging: Always use ./.loom/scripts/merge-pr.sh <PR_NUMBER> to merge PRs. Never use gh pr merge -- it cannot clean up worktree-linked branches and causes stale worktree errors. The merge script handles forge API merge and worktree cleanup automatically.
Finding Work
Champions prioritize work in the following order:
Priority 1: Safe PRs Ready to Auto-Merge
Find Judge-approved PRs ready for merge:
gh pr list \
--label="loom:pr" \
--state=open \
--limit=500 \
--json number,title,additions,deletions,mergeable,updatedAt,files,statusCheckRollup,labels \
--jq '.[] | "#\(.number) \(.title)"'
If found, read and follow instructions in .claude/commands/loom/champion-pr-merge.md.
Priority 2: Quality Issues Ready to Promote
If no PRs need merging, check for curated issues. Exclude loom:evaluating (a
fresh claim from a concurrent Champion evaluation, #4954), as well as
loom:operator-only and loom:blocked — both put an issue permanently outside
Champion's promotion authority per champion-issue-promo.md's "When NOT to
Promote", so there is no reason to hand them into the evaluation pass at all
(#5163). Also exclude loom:issue and loom:building — promotion adds
loom:issue but deliberately leaves loom:curated in place as a permanent
milestone marker (see note below), so without this exclusion every
already-promoted or already-claimed issue keeps matching this query forever
(#5285). Excluding them here, not just in the evaluation step, so a batch
doesn't re-discover work another pass already claimed or that is already
terminal — title/body feed champion-issue-promo.md's body-hash
idempotency check (the issue's aggregate updatedAt is deliberately NOT used
for it, #4966):
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 · 311 lines · 0 tokens per session scan A 89b94ee7699f
champion 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 3,713 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
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
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.
ship
Ship is the operational release-prep flow for a connected project repo.
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.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.