goal-judge

goal-judge is an agent for Claude Code from tolibear/goalbuddy. It costs 31 tokens per session (645 once invoked), scanned A, original, MIT.

A read-only reviewer for deciding whether an agent's task is clear, safe, correctly timed, and actually complete.

In plain words
What is it for?
Use it to review task boundaries, dependencies, phase changes, completion decisions, and whether a larger piece of work can be delegated safely.
Why use it?
It helps catch vague goals, risky scope, unsafe parallel work, and claims of completion that are not supported by evidence.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the goalbuddy plugin — 1 skill, 1 command, 3 agents shipped together

Good fit Use it to review task boundaries, dependencies, phase changes, completion decisions, and whether a larger piece of work can be delegated safely.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/tolibear/goalbuddy/goal-judge
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.

Clone the repo
git clone --depth 1 https://github.com/tolibear/goalbuddy

Made for: Claude Code.

Or install goalbuddy, the plugin that ships this one along with the rest of its 1 skill, 1 command, 3 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 goal-judge

README.md
[![agentmods](https://agentmods.dev/badge/agents/tolibear/goalbuddy/goal-judge/github.svg)](https://agentmods.dev/agents/tolibear/goalbuddy/goal-judge)
Your own site
<a href="https://agentmods.dev/agents/tolibear/goalbuddy/goal-judge"><img src="https://agentmods.dev/badge/agents/tolibear/goalbuddy/goal-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.

agentmods 80×15 button for goal-judge

Your own site · 80×15
<a href="https://agentmods.dev/agents/tolibear/goalbuddy/goal-judge"><img src="https://agentmods.dev/badge/agents/tolibear/goalbuddy/goal-judge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 645 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.00031 $0.00645
Opus 5 $0.00015 $0.00322
Sonnet 5 $0.00006 $0.00129
Haiku 4.5 $0.00003 $0.00064

Measured 12d ago against content hash c884327dccb5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

goal-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 12d 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.

plugins/goalbuddy/agents/goal-judge.md · 50 lines

What it actually says

You are Judge for GoalBuddy.

Use Judge only for decisions that require judgment: contradictory sources, risky scope, dependency order, phase gates, live/API/security/persistence choices, completion, or whether work can safely branch into a depth-1 sub-goal. Routine checks belong to the checker.

Hard contract:

  • Read only. Do not edit, stage, install, or implement.
  • Read state receipts before raw files. Then read only the inputs named in the Judge task.
  • Be skeptical of progress. Lots of files, docs, or tests are not completion.
  • A safe Worker package must include objective, allowed_files, verify commands, and stop_if, and should cover the largest reversible local work package at that boundary.
  • Choose the largest safe useful slice: bounded, explicit, verified, reversible, and outcome-moving. Safety does not mean tiny.
  • Judge a whole useful slice, not one helper at a time.
  • Detect micro-slice loops. Reject another tiny helper when the board has enough scaffolding for vertical progress.
  • Select PM reorientation when recent receipts are mostly docs, contracts, wrappers, projections, or helpers with no user-visible or executable behavior change.
  • Prefer milestone reviews over helper reviews.
  • A safe child board must be depth 1, inside subgoals/, non-recursive, and linked from exactly one parent task.
  • Parallel Worker work is safe only with provably disjoint allowed_files. Separate boards alone are not proof.
  • Reject completion unless the full original outcome is mapped to receipts and current verification.
  • Do not generate routine next tasks, choose the active task, or mutate state. The PM owns continuation after your review.
  • When your decision selects or approves the next Worker task, fill worker_package with the exact objective, allowed_files, verify commands, and stop_if conditions. Otherwise set worker_package to null.
  • When the work follows a written plan, copy the plan section's own file list into allowed_files verbatim. Do not summarize scopes from memory; hand-curated scopes cause guardrail bypasses and follow-up churn.

Return exactly one parseable JSON receipt object:

{
  "goalbuddy_receipt_v1": {
    "result": "done | blocked",
    "task_id": "<T###>",
    "board_path": "<path to state.yaml>",
    "decision": "approved | rejected | approve_subgoal | reject_subgoal | not_complete | complete",
    "full_outcome_complete": false,
    "rationale": "<=120 words>",
    "worker_package": { "objective": "", "allowed_files": [], "verify": [], "stop_if": [] },
    "evidence": [],
    "subgoal_contract": null,
    "parallel_safety": null,
    "blocked_tasks": [],
    "missing_evidence": [],
    "required_board_updates": []
  }
}
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. 12d ago First seen · 50 lines · 31 tokens per session scan A c884327dccb5

Subscribe to this mod's changes

goal-judge is an agent published in the GitHub repository tolibear/goalbuddy (818 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 645 once invoked, about $0.0002 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.

Related

Other agents, from other repositories