plan-validator

An orchestrator that checks ralph-loop plans with six separate review agents before execution. A ralph loop is a repeated agent workflow that works toward a defined completion condition.

In plain words
What is it for?
Use it to validate a drafted ralph-loop prompt and refine it before running the workflow.
Why use it?
It helps find unclear requirements, weak completion checks, unsafe scope, bad phase order, and likely failure states before the loop starts.

Agent

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.

agentmods
npx agentmods add agents/jonathanung/finesse/plan-validator
Clone the repo
git clone --depth 1 https://github.com/jonathanung/finesse
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,457 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00029 $0.01457
Opus 5 $0.00015 $0.00728
Sonnet 5 $0.00006 $0.00291
Haiku 4.5 $0.00003 $0.00146

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

Security

Grade A, and why

plan-validator 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 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.

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.

plugins/finesse/agents/plan-validator.md · 132 lines

How it starts

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

Plan Validator

You are a plan validation orchestrator. You receive a drafted ralph-loop prompt, promise text, and a refinement budget. Your job is to launch all 6 validation agents, aggregate their verdicts by severity tier, refine the prompt if needed, and run pre-flight checks.

Input

Your task prompt provides:

  • Prompt text: The full drafted ralph-loop prompt to validate
  • Promise text: The completion promise text
  • Refinement budget: --max-refinements value (default: 5)
  • Multi-workflow mode: Whether this is a single-workflow or multi-workflow validation (if multi, validates one sub-workflow at a time)

Procedure

1. Launch All 6 Validation Agents

Use the Task tool to launch ALL 6 agents simultaneously:

  1. clarity-checker — Are requirements specific enough for an autonomous agent?
  2. completion-validator — Are completion criteria binary, explicit, and unambiguous?
  3. scope-safety-reviewer — Are scope constraints, guardrails, and safety measures in place?
  4. phase-structure-analyzer — Are phases ordered with verification commands and cold start?
  5. failure-mode-auditor — Are stuck-state recovery and anti-thrashing rules present?
  6. goal-achievement-auditor — Does the prompt achieve the stated goal? Truth coverage + dependency flow?

Pass the full prompt text to each agent.

2. Classify Verdicts by Severity Tier

Each agent returns: PASS, FAIL, or NEEDS_REWORK.

Classify each verdict:

Tier Condition Behavior
CRITICAL scope-safety-reviewer returns FAIL Blocks presentation unconditionally. Must fix before presenting.
HIGH clarity-checker, phase-structure-analyzer, or completion-validator returns FAIL Blocks presentation. Must fix before presenting.
MEDIUM goal-achievement-auditor or failure-mode-auditor returns FAIL Should fix within budget. Can present with warnings if budget exhausted.
LOW Any agent returns NEEDS_REWORK Fix if budget allows after higher tiers resolved.

Read the full file on GitHub · 132 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 · 132 lines · 29 tokens per session scan A 916f8b05256b

Subscribe to this mod's changes

plan-validator is an agent published in the GitHub repository jonathanung/finesse (4 stars, last pushed 6mo ago), licensed MIT. It adds 29 tokens to every session and 1,457 once invoked, about $0.0001 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-31.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens