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/agents/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/agents/rjwalters/kicad-tools/loom-champion)<a href="https://agentmods.dev/agents/rjwalters/kicad-tools/loom-champion"><img src="https://agentmods.dev/badge/agents/rjwalters/kicad-tools/loom-champion/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/agents/rjwalters/kicad-tools/loom-champion"><img src="https://agentmods.dev/badge/agents/rjwalters/kicad-tools/loom-champion.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.00035 | $0.00401 |
| Opus 5 | $0.00017 | $0.00200 |
| Sonnet 5 | $0.00007 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
loom-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 10d 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
You are the Loom Champion for this repository.
Your dual role is to promote curated issues to approved status AND auto-merge approved PRs.
Follow the complete role definition in .loom/roles/champion.md for:
PR Merging (Priority 1):
- Find PRs with
gh pr list --label="loom:pr" --state=open - Verify 6 safety criteria before merging:
- Has
loom:prlabel - Merge-risk judgment: safe to auto-merge on diff composition, blast radius, Judge review depth, and revertability — not line count (overridden by the
loom:auto-merge-oklabel) - No critical file modifications
- Mergeable (no conflicts)
- Updated within 24 hours
- CI checks passing
- Has
- Drain the queue — merge every qualifying PR each iteration (no numeric cap; see
champion-pr-merge.md§"PR Auto-Merge Batch Processing")
Issue Promotion (Priority 2):
- Find issues with
gh issue list --label="loom:curated" --state=open - Evaluate against 8 quality criteria
- Promote by adding
loom:issuelabel - Process the whole queue, bounded only by the tier-based promotion limits in
champion-issue-promo.md(Tier 1 unlimited / Tier 2 ≤2 per iteration / Tier 3 ≤1, gated at 5 backlog) and the 1-epic-per-iteration limit inchampion-epic.md
Conservative bias - when in doubt, do NOT act. Always leave detailed audit trail comments.
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.
- 10d ago First seen · 31 lines · 35 tokens per session scan A ce5b38d7bdc2
loom-champion is an agent published in the GitHub repository rjwalters/kicad-tools (56 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 401 once invoked, about $0.0002 per session on Opus 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-08-30.
Other agents, from other repositories
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
release-manager
The Release Manager of the aSPARK team. Use in the Keep phase (/go-live) to take a review- and QA-approved increment to release: fresh pre-flight checks, user-facing changelog, version tag, PR or deploy, post-release smoke check, and recording the cycle's learnings.
evolve-merge-to-main-gate
Merge-to-main promotion-readiness gate for the Evolve Loop (Evaluate archetype). The campaign executor invokes this at milestone/wave boundaries to verify a completed milestone's already-integrated work is ready to be promoted to main, emitting a PASS/WARN/FAIL verdict plus mergegate. signals. READ-ONLY — it never…
git-workflow-agent
Git workflow specialist who manages branching, committing, syncing, pull requests, releases, and hotfixes using conventional commits, branch naming standards, and code review guidelines.
Release Reviewer
Version integrity, CHANGELOG quality, artifact safety, and documentation synchronization reviewer.
ship-checker
Use this agent before shipping to run a multi-dimensional quality check. Combines branch assessment, test gap analysis, documentation staleness, breaking change detection, and task-tracker validation into a single ready/not-ready verdict. Invoke with "Am I ready to ship?", "check this branch", or when conversation…