Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add closedloop-ai/claude-plugins/plugin install judgesWrote 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/skills/closedloop-ai/claude-plugins/run-judges)<a href="https://agentmods.dev/skills/closedloop-ai/claude-plugins/run-judges"><img src="https://agentmods.dev/badge/skills/closedloop-ai/claude-plugins/run-judges/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/skills/closedloop-ai/claude-plugins/run-judges"><img src="https://agentmods.dev/badge/skills/closedloop-ai/claude-plugins/run-judges.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.00099 | $0.15087 |
| Opus 5 | $0.00049 | $0.07544 |
| Sonnet 5 | $0.00020 | $0.03017 |
| Haiku 4.5 | $0.00010 | $0.01509 |
Grade C, and why
run-judges scanned grade C with 2 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 yesterday.
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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -LsSf https://astral.sh/uv/install.sh | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -LsSf https://astral.sh/uv/install.sh | sh How it starts
The opening of the file, as written. The whole thing — 1,296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Judges Skill
Purpose
Execute specialized judge agents in parallel to evaluate implementation plan quality (16 judges, 4 batches), code quality (11 judges, 3 batches), PRD quality (5 judges, 2 batches), or Feature quality (3 judges, 1 batch). All batches respect the Task tool's 4-concurrent-agent limit. Aggregates results into $CLOSEDLOOP_WORKDIR/plan-judges.json (plan), $CLOSEDLOOP_WORKDIR/code-judges.json (code), $CLOSEDLOOP_WORKDIR/prd-judges.json (prd), or $CLOSEDLOOP_WORKDIR/feature-judges.json (feature) with validated output format.
Parameters
--workdir: Path to the working directory containing judge artifacts (optional)
- Resolved in order:
--workdirargument →$CLOSEDLOOP_WORKDIRenvironment variable →.closedloop-ai/judges(default, relative to current working directory) - The directory is created automatically if it does not exist
- All output files (
plan-judges.json,code-judges.json,prd-judges.json,judge-input.json,perf.jsonl, etc.) are written to this resolved directory
--artifact-type: Artifact category to evaluate (plan | code | prd | feature), default: plan
- plan (default): Evaluate implementation plan with 16 judges, 4 batches, output to plan-judges.json
- code: Evaluate implemented code with 11 judges, 3 batches, output to code-judges.json
- prd: Evaluate PRD document with 5 judges across 2 sequential batches (3 + 2, max 4 concurrent per batch), output to prd-judges.json
- feature: Evaluate Feature artifact with 3 judges, 1 batch, output to feature-judges.json
Judge Input Contract (judge-input.json)
The judge input contract is maintained in:
skills/run-judges/references/judge-input-contract.md (resolve to an absolute path at runtime via Glob)
This keeps orchestration flow readable while preserving a single source of truth for contract fields and semantics.
run-judges is the producer chokepoint for judge-input.json. After mode-specific context preparation and before launching any judge agent, invoke the deterministic mapper:
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/judge-input-contract.md 2.7 KB
- scripts/ensure_agents_snapshot.sh 2.6 KB runs code
- scripts/judge_input_mapping.py 22 KB runs code
- scripts/test_judge_agent_input_contract.py 3.3 KB runs code
- scripts/test_judge_input_mapping.py 11 KB runs code
- scripts/test_validate_judge_report.py 43 KB runs code
- scripts/validate_judge_report.py 7.7 KB runs code
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.
- yesterday First seen · 1,296 lines · 99 tokens per session scan C f2eea0d366d6
run-judges is a skill published in the GitHub repository closedloop-ai/claude-plugins (103 stars, last pushed 2d ago), licensed Apache-2.0. It adds 99 tokens to every session and 15,087 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.
Other skills, from other repositories
pr-reviewer
Reviews a diff or security scope read-only using evidence-tiered findings, structural and context-error rubrics, and repository review policy. Use when asked to "review my changes", "structural review", "review for AI patterns", or "security audit". For applying fixes use tidy; for UI defects use ui-design.
pr-babysitter
Monitors or repairs an open GitHub PR: CI failures, conflicts, review threads, and merge readiness, reporting state changes. Use when asked to "watch this PR", "fix CI", "resolve conflicts", or "address review comments". For PR metadata use pr-creator; for npm release PRs use autoship.
dx-audit
Audits libraries, CLIs, and SDKs using 38 rules for public contracts, package exports, piped output, errors, and configuration. Use when asked to "audit my CLI", "review my SDK", "make this agent-friendly", or diagnose package type resolution. For agentic product trust use ax-audit; for docs use docs-writing.
pr-creator
Creates or updates GitHub PRs with house-style titles and bodies, issue linking, repository templates, and draft state. Use when asked to "create a PR", "rewrite the PR description", or "polish this PR". For code fixes use tidy; for CI and review threads use pr-babysitter; for npm releases use autoship.
tidy
Applies diff-scoped simplifications using reuse, ownership, efficiency, and test-value checks, including actionable review findings. Use when asked to "tidy this", "simplify my diff", or "apply the review findings". For a read-only report use pr-reviewer; for repository architecture use codebase-architecture.
id-impact
Two advisory pre-merge reads of an infra-delivery change. (v2) The POLICY-RISK read — surface foundryplanmodel.parsepolicyfindings output {rule, resource, severity, gating} and distinguish hard-FAIL-shaped (gating==deny) vs ackable-shaped (gating==warn ∧ severity==high ⇒ freeze a policy:high-blast-ack {rule…