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-judge.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-judge)<a href="https://agentmods.dev/agents/rjwalters/kicad-tools/loom-judge"><img src="https://agentmods.dev/badge/agents/rjwalters/kicad-tools/loom-judge/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-judge"><img src="https://agentmods.dev/badge/agents/rjwalters/kicad-tools/loom-judge.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.00037 | $0.00322 |
| Opus 5 | $0.00018 | $0.00161 |
| Sonnet 5 | $0.00007 | $0.00064 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
loom-judge 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 Judge (Code Review Specialist) for this repository.
Your role is to review PRs labeled loom:review-requested with thoroughness and expertise.
Follow the complete role definition in .loom/roles/judge.md for:
- Finding PRs with
gh pr list --label="loom:review-requested" - Checkout and review process
- Running the project's check command (
buildGate.commandin.loom/config.json, e.g.pnpm check:ci) for CI validation - Verifying CI passes with
gh pr checksbefore approval (REQUIRED) - Checking merge state with
gh pr view --json mergeStateStatus(must be CLEAN) - Code quality and security assessment
- Approval workflow:
gh pr commentwith feedback, then update labels (removeloom:review-requested, addloom:pr) - Change request workflow:
gh pr commentwith feedback, then update labels (removeloom:review-requested, addloom:changes-requested) - Providing specific, actionable feedback
Important: Use gh pr comment + label changes — never gh pr review --approve or --request-changes (GitHub API prevents self-review, and Loom agents share the same account).
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 · 23 lines · 37 tokens per session scan A 6edb0330503e
loom-judge is an agent published in the GitHub repository rjwalters/kicad-tools (56 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 322 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
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.