run-judges

run-judges is a skill for Claude Code from closedloop-ai/claude-plugins. It costs 99 tokens per session (15,087 once invoked), scanned C, original, Apache-2.0.

A workflow for running several judge agents in parallel to assess a plan, code, PRD, or feature. It combines their results into a checked JSON report.

In plain words
What is it for?
Use it to evaluate implementation plans, source code, product requirements documents, or feature descriptions and save the corresponding judge report.
Why use it?
A single review can miss problems or reflect one reviewer’s view. Multiple specialized evaluations provide separate quality checks while producing a structured result file.

Skill for Claude Code

Written for Claude Code: context: fork in frontmatter. Also seen: mentions subagents.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the judges plugin — 3 skills, 22 agents shipped together

Good fit Use it to evaluate implementation plans, source code, product requirements documents, or feature descriptions and save the corresponding judge report.

Compare 6 skills from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add closedloop-ai/claude-plugins
Claude Code
/plugin install judges

Made for: Claude Code.

Or install judges, the plugin that ships this one along with the rest of its 3 skills, 22 agents.

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 run-judges

README.md
[![agentmods](https://agentmods.dev/badge/skills/closedloop-ai/claude-plugins/run-judges/github.svg)](https://agentmods.dev/skills/closedloop-ai/claude-plugins/run-judges)
Your own site
<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.

agentmods 80×15 button for run-judges

Your own site · 80×15
<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>
Per session 99 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 15,087 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 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.00099 $0.15087
Opus 5 $0.00049 $0.07544
Sonnet 5 $0.00020 $0.03017
Haiku 4.5 $0.00010 $0.01509

Measured yesterday against content hash f2eea0d366d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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.

The scan reads SKILL.md. This mod also ships 6 executable files (scripts/ensure_agents_snapshot.sh, scripts/judge_input_mapping.py, scripts/test_judge_agent_input_contract.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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
plugins/judges/skills/run-judges/SKILL.md · 1,296 lines

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: --workdir argument → $CLOSEDLOOP_WORKDIR environment 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:

Read the full file on GitHub · 1,296 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. yesterday First seen · 1,296 lines · 99 tokens per session scan C f2eea0d366d6

Subscribe to this mod's changes

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.

Related

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.

mblode/agent-skills · 68 tokens

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.

mblode/agent-skills · 72 tokens

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.

mblode/agent-skills · 76 tokens

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.

mblode/agent-skills · 75 tokens

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.

mblode/agent-skills · 68 tokens

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…

lukasrepublic/agentic-foundry · 199 tokens