champion-epic-standdown

champion-epic-standdown is a command for Claude Code from rjwalters/kicad-tools. It costs 0 tokens per session (1,897 once invoked), scanned A, original, MIT.

A Champion workflow step that checks whether a large issue has already been split into smaller tasks before creating more tasks.

In plain words
What is it for?
It is for deciding whether an epic should stand down and simply be monitored until its existing child issues are complete.
Why use it?
It prevents duplicate Phase 1 work when an epic was decomposed manually or by another process.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./.loom/scripts/post-comment.sh "$EPIC_NUMBER" --body "$UMBRELLA_MARKER.

Good fit It is for deciding whether an epic should stand down and simply be monitored until its existing child issues are complete.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/rjwalters/kicad-tools
agentmods
npx agentmods add commands/rjwalters/kicad-tools/champion-epic-standdown

Made for: Claude Code.

Wrote 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.

agentmods badge for champion-epic-standdown

README.md
[![agentmods](https://agentmods.dev/badge/commands/rjwalters/kicad-tools/champion-epic-standdown/github.svg)](https://agentmods.dev/commands/rjwalters/kicad-tools/champion-epic-standdown)
Your own site
<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/champion-epic-standdown"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/champion-epic-standdown/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.

agentmods 80×15 button for champion-epic-standdown

Your own site · 80×15
<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/champion-epic-standdown"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/champion-epic-standdown.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,897 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01897
Opus 5.5 $0.00000 $0.00759
Sonnet 5.5 $0.00000 $0.00379
Haiku 4.5 $0.00000 $0.00190

Measured 2d ago against content hash c59dd395ae8d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

champion-epic-standdown 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 2d 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.

.claude/commands/loom/champion-epic-standdown.md · 118 lines

How it starts

The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Champion: Step 0.5 — Tracking-Umbrella Stand-Down (#7666)

This file is the body of champion-epic.md → "Step 0.5". Read it when that step tells you to, after Step 0's Completion-First Check has declined to act and before Step 1. It answers the one question the 6 structural criteria cannot: "has this epic already been decomposed, by someone other than Step 3?"

The 6 criteria describe an epic awaiting decomposition — they check the phases, sizing, and success criteria Step 3 needs in order to create Phase 1 issues. An epic whose children already exist and are being worked is past that point. Those children may come from a Curator decomposition pass, native GitHub sub-issues, or a hand-written - [ ] #N task list, none of which carries the <!-- loom:epic:$EPIC_NUMBER:phase:N --> marker that Step 2.75 and "Detecting Phase Completion" search for — so neither phase creation nor phase progression can see them, and a literal reading of Step 2.75 would report EXISTING_COUNT=0 and create a duplicate Phase 1 set. Champion has nothing left to do for such an epic except watch it finish, which Step 0 already does on every pass. A passing epic is never a stuck epic: the correct handling is one durable note and then silence — never a structural re-evaluation, never an operator escalation.

0.5a. Detect the tracking umbrella

Reuses Step 0a's discovery — do NOT re-run discover_epic_children.

# Set by Step 0a: EPIC_CHILD_STRONG_{OPEN,CLOSED}, EPIC_CHILD_SOURCES.
# `phase-marker` in EPIC_CHILD_SOURCES means discovery source (a) contributed,
# i.e. Champion decomposed this epic itself and "Phase Progression" owns it
# from here — such an epic must fall through to Step 1 exactly as before.
case ",$EPIC_CHILD_SOURCES," in
  *,phase-marker,*)
    IS_TRACKING_UMBRELLA=no ;;                  # Champion's own decomposition
  *)
    if [ "$EPIC_CHILD_STRONG_OPEN" -gt 0 ]; then
      IS_TRACKING_UMBRELLA=yes                  # decomposed elsewhere, still in flight
    else
      IS_TRACKING_UMBRELLA=no                   # undecomposed (Step 1), or complete (Step 0 owned it)
    fi ;;
esac

Read the full file on GitHub · 118 lines

Changes

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.

  1. 2d ago Changed c59dd395ae8d
  2. 15d ago Changed ade44849120f
  3. 1mo ago First seen · 118 lines · 0 tokens per session scan A f4bf698413d9

Subscribe to this mod's changes

champion-epic-standdown is a command published in the GitHub repository rjwalters/kicad-tools (70 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,897 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-09-17.