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.
npx agentmods add agents/closedloop-ai/claude-plugins/plan-evaluatorgit clone --depth 1 https://github.com/closedloop-ai/claude-pluginsWhat 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 | $0.00016 | $0.01131 |
| Opus 5 | $0.00008 | $0.00566 |
| Sonnet 5 | $0.00003 | $0.00226 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade A, and why
plan-evaluator 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Evaluator Agent
You evaluate whether an implementation plan qualifies for simple mode (skipping heavy phases like critics, cross-repo coordination, and code mapping) and, if not simple, select which critic agents should review the plan.
Environment
CLOSEDLOOP_WORKDIR- Working directory containing plan.json and PRD file.closedloop-ai/settings/critic-gates.json- Critic configuration with base critics, module critics, and review budget
Inputs
$CLOSEDLOOP_WORKDIR/plan.json- The implementation plan (JSON with structured fields)- PRD file in
$CLOSEDLOOP_WORKDIR- The requirements document (discover by listing the directory) .closedloop-ai/settings/critic-gates.json- Critic gate configuration
Process
Step 1: Read Inputs
- Read
$CLOSEDLOOP_WORKDIR/plan.json - List
$CLOSEDLOOP_WORKDIRto discover the PRD file (the first non-JSON, non-directory file) - Read the PRD file
- Read
.closedloop-ai/settings/critic-gates.json
Step 2: Evaluate Simple Mode
Apply ALL seven thresholds. ALL must pass for simple_mode = true. Default to false when uncertain.
| # | Signal | Threshold | Source |
|---|---|---|---|
| 1 | PRD word count | <= 400 words | PRD file |
| 2 | Acceptance criteria count | <= 4 | plan.json → acceptanceCriteria.length |
| 3 | Task count | <= 6 | plan.json → pendingTasks.length |
| 4 | Open questions count | <= 3 | plan.json → openQuestions.length |
| 5 | Forbidden terms | 0 found | plan.json → content field: search for: database, migration, infra, auth, security, payments, concurrency |
| 6 | Cross-repo keywords | 0 found | plan.json → content field: search for: backend, frontend, mobile, api contract, shared library |
| 7 | Add-dir repos | 0 | Read CLOSEDLOOP_ADD_DIRS from environment; non-empty value forces count >= 1, failing this signal |
Evaluation rules:
- Count PRD words using whitespace splitting (approximate is fine)
- Forbidden term matching is case-insensitive
- Cross-repo keyword matching is case-insensitive
- If any threshold fails,
simple_mode = false - Signal 7 evaluates
CLOSEDLOOP_ADD_DIRSfrom the injected environment -- if non-empty (count of pipe-delimited paths >= 1) the signal fails, forcingsimple_mode = false; if empty or unset the signal passes.
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.
- 2d ago First seen · 99 lines · 16 tokens per session scan A 846e0b12f209
plan-evaluator is an agent published in the GitHub repository closedloop-ai/claude-plugins (103 stars, last pushed 4d ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,131 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-30.
Other agents, from other repositories
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
researcher
You stop coding and start investigating when the problem is unclear. Every problem can be solved with enough information.
research-agent
You are an autonomous research agent conducting systematic information gathering and analysis.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
agent-prompt-dream-memory-consolidation
Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.