plan-critique-loop

plan-critique-loop is a skill for Claude Code, Codex from besimple-oss/broccoli. It costs 45 tokens per session (1,352 once invoked), scanned A, original, MIT.

A review cycle for an existing written implementation plan. It checks the plan, sorts feedback into accepted or rejected points, revises it, and repeats this for up to three rounds.

In plain words
What is it for?
Use it when a plan document already exists and you want structured critique and revision before starting implementation.
Why use it?
It helps find missing details or weak decisions before coding begins. The workflow is limited to improving the plan and does not implement the work.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; positional $N argument; mentions Claude Code.

Good fit Use it when a plan document already exists and you want structured critique and revision before starting implementation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/besimple-oss/broccoli/plan-critique-loop
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add besimple-oss/broccoli --skill plan-critique-loop
Clone the repo
git clone --depth 1 https://github.com/besimple-oss/broccoli

Made for: Claude Code, Codex.

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 plan-critique-loop

README.md
[![agentmods](https://agentmods.dev/badge/skills/besimple-oss/broccoli/plan-critique-loop/github.svg)](https://agentmods.dev/skills/besimple-oss/broccoli/plan-critique-loop)
Your own site
<a href="https://agentmods.dev/skills/besimple-oss/broccoli/plan-critique-loop"><img src="https://agentmods.dev/badge/skills/besimple-oss/broccoli/plan-critique-loop/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 plan-critique-loop

Your own site · 80×15
<a href="https://agentmods.dev/skills/besimple-oss/broccoli/plan-critique-loop"><img src="https://agentmods.dev/badge/skills/besimple-oss/broccoli/plan-critique-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,352 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.00045 $0.01352
Opus 5.5 $0.00018 $0.00541
Sonnet 5.5 $0.00009 $0.00270
Haiku 4.5 $0.00005 $0.00135

Measured 1mo ago against content hash 55d9cef68e94, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plan-critique-loop 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 1mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/run_critique_loop.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.

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.

prompt-templates/skills/plan-critique-loop/SKILL.md · 100 lines

How it starts

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

Plan Critique Loop (up to 3 iterations)

Input: an existing plan doc path (for example: plan/my-feature.md).

Preconditions

  • Confirm you are in the intended repo: git rev-parse --show-toplevel
  • Confirm the plan doc exists: test -f <plan-doc-path>
  • Ensure git can create commits before running the loop (user.name/user.email configured).
  • Do not start implementation in this skill; only critique and revise the plan.
  • Ensure both CLIs are available (codex and claude) because critic/responder must be different vendors.

Expected runtime

Typically runs 15–45 minutes, but allow at least 120 minutes.

Do not interrupt/restart the subagent if it looks stuck. The loop script owns stuck/timeout handling and will exit on its own when it completes or when --timeout is reached. Prefer watching the periodic heartbeat output (--heartbeat-seconds) instead of tailing logs.

If you use --progress-log, do not tail -f it into the main context unless you must debug; prefer checking progress via log line counts (for example: wc -l <progress-log>) and/or the heartbeat counters.

Why Claude sometimes looked “stuck”

Claude Code print mode can be silent in --output-format text until it finishes (including during tool work). This repo defaults Claude subprocesses to --output-format stream-json --include-partial-messages so the wrapper sees measurable progress and inactivity timeouts mainly trigger on true hangs.

Loop

Run the critique loop script:

resolve_skill_dir() {
  local name="$1"
  local repo_root=""
  repo_root="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"

  local candidates=(
    "$repo_root/.agents/skills/$name"
    "$repo_root/.claude/skills/$name"
    "$HOME/.agents/skills/$name"
    "$HOME/.codex/skills/$name"
    "$HOME/.claude/skills/$name"
  )

  for d in "${candidates[@]}"; do
    if [[ -d "$d" ]]; then
      echo "$d"
      return 0
    fi
  done

  echo "Error: skill '$name' not found in repo-scoped or user-scoped skill dirs." >&2
  return 1
}

PLAN_CRITIQUE_LOOP_SKILL_DIR="$(resolve_skill_dir plan-critique-loop)"
python3 "$PLAN_CRITIQUE_LOOP_SKILL_DIR/scripts/run_critique_loop.py" <plan-doc-path>

Read the full file on GitHub · 100 lines

Files

What ships with it

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

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. 1mo ago First seen · 100 lines · 45 tokens per session scan A 55d9cef68e94

Subscribe to this mod's changes

plan-critique-loop is a skill published in the GitHub repository besimple-oss/broccoli (283 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 1,352 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories

submit-review

Reference for how a finished ticket reaches human review in the Gaffer factory. Submission is RUNNER-OWNED — the agent commits its work and evidences the ACs, then stops; the runner records the delivery and submits for review (and pushes / opens a PR only when the operator enabled that). Invoke when you think your…

tmj-90/gaffer · 105 tokens

cc-autopilot

Run cc-autopilot, a perpetual autonomous AUDIT/GENERATE→TRIAGE→BATCH→FIX→VERIFY→REVIEW→COMMIT loop that holds every change to a configured quality bar through a judge panel. Its fixers each own a file-disjoint slice of the tree so no two can ever touch the same file, and nothing unverified reaches git. Works on a web…

gbotev1/cc-autopilot · 155 tokens

github-code-review

Comprehensive GitHub code review with AI-powered swarm coordination.

airmcp-com/mcp-standards · 15 tokens

github-pr-workflow

Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.

paperclipai/paperclip · 39 tokens

github-automation

GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.

ruvnet/ruflo · 61 tokens

handoff-spec

Hand a spec that is mid-implementation to another machine or another agent.

dzhng/skills · 19 tokens