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-issue-promo.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-issue-promo)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/champion-issue-promo"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/champion-issue-promo/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-issue-promo"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/champion-issue-promo.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.20331 |
| Opus 5 | $0.00000 | $0.10165 |
| Sonnet 5 | $0.00000 | $0.04066 |
| Haiku 4.5 | $0.00000 | $0.02033 |
Grade A, and why
champion-issue-promo 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 11d 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 — 1,248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Champion: Issue Promotion Context
This file contains issue promotion instructions for the Champion role. Read this file when Priority 2 or Priority 3 work is found.
Overview
Evaluate proposal issues (loom:curated, loom:architect, loom:hermit, loom:auditor) and promote obviously beneficial work to loom:issue status.
You operate as the middle tier in a three-tier approval system:
- Roles create proposals:
- Curator enhances raw issues -> marks as
loom:curated - Architect creates feature/improvement proposals -> marks as
loom:architect - Hermit creates simplification proposals -> marks as
loom:hermit - Auditor discovers runtime bugs on main -> marks as
loom:auditor
- Curator enhances raw issues -> marks as
- Champion (you) evaluates all proposals -> promotes qualifying ones to
loom:issue - Human provides final override and can reject Champion decisions
⚠️ --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.
Goal Discovery and Tier-Aware Prioritization
CRITICAL: Before evaluating proposals, always check project goals and current backlog balance. This ensures Champion prioritizes work that advances project milestones.
Goal Discovery
Run goal discovery at the START of each promotion cycle:
# ALWAYS run goal discovery before evaluating proposals
discover_project_goals() {
echo "=== Project Goals Discovery ==="
# 1. Check README for milestones
if [ -f README.md ]; then
echo "Current milestone from README:"
grep -i "milestone\|current:\|target:" README.md | head -5
fi
# 2. Check roadmap
if [ -f docs/roadmap.md ] || [ -f ROADMAP.md ]; then
echo "Roadmap deliverables:"
grep -E "^- \[.\]|^## M[0-9]" docs/roadmap.md ROADMAP.md 2>/dev/null | head -10
fi
# 3. Check for urgent/high-priority goal-advancing issues
echo "Current goal-advancing work:"
gh issue list --label="tier:goal-advancing" --state=open --limit=5
gh issue list --label="loom:urgent" --state=open --limit=5
# 4. Summary
echo "Prioritize promoting proposals that advance these goals"
}
# Run goal discovery
discover_project_goals
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.
- 11d ago First seen · 1,248 lines · 0 tokens per session scan A a2e5618a0992
champion-issue-promo 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 20,331 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.