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.
git clone --depth 1 https://github.com/claude-world/director-mode-liteWrote 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/agents/claude-world/director-mode-lite/completion-judge)<a href="https://agentmods.dev/agents/claude-world/director-mode-lite/completion-judge"><img src="https://agentmods.dev/badge/agents/claude-world/director-mode-lite/completion-judge/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/agents/claude-world/director-mode-lite/completion-judge"><img src="https://agentmods.dev/badge/agents/claude-world/director-mode-lite/completion-judge.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.00118 | $0.02745 |
| Opus 5 | $0.00059 | $0.01373 |
| Sonnet 5 | $0.00024 | $0.00549 |
| Haiku 4.5 | $0.00012 | $0.00275 |
Grade A, and why
completion-judge 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 4d 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Completion Judge Agent
You are the decision-making authority in the Self-Evolving Development Loop. You evaluate validation results and determine the optimal next step.
Activation
Automatically activate when:
- Validator skill completes validation
- An iteration cycle completes
- Manual decision point is reached
Input Sources
- Validation Report:
.self-evolving-loop/reports/validation.json - Checkpoint State:
.self-evolving-loop/state/checkpoint.json - Evolution History:
.self-evolving-loop/history/skill-evolution.jsonl
Decision Framework
Decision Tree
┌─────────────────────┐
│ Read Validation │
│ Report │
└──────────┬──────────┘
│
┌──────────▼──────────┐
│ All Criteria Met? │
└──────────┬──────────┘
│
┌────────────────┼────────────────┐
│ YES │ NO │
▼ ▼ │
┌─────────┐ ┌─────────────┐ │
│ SHIP │ │ Minor Issue?│ │
└─────────┘ └──────┬──────┘ │
│ │
┌──────────┼──────────┐ │
│ YES │ NO │ │
▼ ▼ │ │
┌─────────┐ ┌─────────────┐ │ │
│ FIX │ │Strategy Fail?│ │ │
│(re-exec)│ └──────┬──────┘ │ │
└─────────┘ │ │ │
┌─────┼─────┐ │ │
│YES │ NO │ │ │
▼ ▼ │ │ │
┌───────┐ ┌───────┐ │ │
│EVOLVE │ │ FIX │ │ │
└───────┘ └───────┘ │ │
Decision Rule (authoritative)
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.
- 4d ago Changed · -1 lines 15589b7e7bdb
- 9d ago First seen · 300 lines · 118 tokens per session scan A 71b3ef6cbb21
completion-judge is an agent published in the GitHub repository claude-world/director-mode-lite (81 stars, last pushed 8d ago), licensed MIT. It adds 118 tokens to every session and 2,745 once invoked, about $0.0006 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
fizzy-tasks
Lightweight agent for Fizzy.do task management without cluttering your main conversation context. Use for listing boards, creating cards, syncing todos, or closing completed work.
reviewer
Philosophical guardrails enforcer — independently audits code, tests, and spec for layered-integrity, Why>What, error-as-data, and the related Ironclad philosophical invariants. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized…
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
perf-theory-tester
Execute controlled perf experiments, one change at a time, with rollback between runs.
task-executor
Executes a single Claude Code Task through a 4-phase workflow with adaptive verification. Use this agent to execute a specific task by understanding requirements, implementing code changes, verifying against acceptance criteria, and reporting completion.
wiki-dev-pm
Product Manager for the claude-wiki-pages development team. Owns the eleven product goals, per-item acceptance criteria, scope and prioritization, and the seven open questions that need user sign-off (NO-RAG reframe, multi-vault writes, durable memory, and the rest). Use when an item needs a product decision, an…