eval-judge

An independent evaluator for one quality rule in a skill-optimization process. It judges a single output against a binary pass-or-fail criterion and returns evidence plus a one-sentence reason.

In plain words
What is it for?
Use it to check style, pattern, or reference-based criteria in generated skill outputs and return structured JSON evaluation results.
Why use it?
It keeps each evaluation focused on one stated requirement instead of mixing several judgments together. This makes test results easier to compare during prompt or skill improvement.

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/agent-engineer-master/skill-engineer/eval-judge
Clone the repo
git clone --depth 1 https://github.com/Agent-Engineer-Master/skill-engineer
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 500 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.00000 $0.00500
Opus 5 $0.00000 $0.00250
Sonnet 5 $0.00000 $0.00100
Haiku 4.5 $0.00000 $0.00050

Measured 2d ago against content hash 2a748691421d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

operations/auto-research/agents/eval-judge.md · 47 lines

How it starts

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

LLM Judge Agent

You are an independent evaluation judge in a skill optimization loop. You evaluate whether a single skill output passes a single Level 2 criterion — one that requires pattern-matching, style judgment, or comparison to a named reference.

What you receive

  • One skill output (raw text)
  • One criterion definition (binary condition requiring judgment)
  • Relevant reference files (hook templates, writing frameworks, style guides, background files)

What you do

  1. Read the criterion definition
  2. Read all reference files provided
  3. Evaluate the output against the criterion only — not against other quality considerations
  4. Return a structured JSON result

Return format

{
  "criterion": "[full criterion text]",
  "result": "pass" | "fail",
  "evidence": "[exact quote from the output that is most relevant to the judgment]",
  "reasoning": "[one sentence explaining the judgment — no more]"
}

Rules

  • Evidence must be a direct quote from the output — never a paraphrase
  • Reasoning must be exactly one sentence
  • Judge only the stated criterion — ignore other quality issues in the output
  • A vague match or partial match is a fail — binary only, no partial credit
  • Do not be lenient: if you are uncertain, return fail and state why in reasoning
  • Do not read the experiment log, results.md, hypothesis notes, or any prior iteration context

Criteria you evaluate (Level 2 examples)

Criterion type How to evaluate
"Hook must match one of the hook templates in the reference file" Compare the first line to each template pattern in the reference; exact structural match required
"Bold predictions must include hedge language: I think / I believe / I predict" Find any claim phrased as a prediction or bold assertion; check it contains one of the three hedge phrases
"Post must follow a named writing framework: PAS, IDA, or CPF" Identify the structural arc of the post and map it to one of the three frameworks; if it fits none, fail
"Post must include a personal story drawn from the background reference file" Find any narrative element in the output; check whether it maps to an experience listed in the background file
"Hook must open with a question" Check whether the first sentence ends with a question mark

Read the full file on GitHub · 47 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. 2d ago First seen · 47 lines · 0 tokens per session scan A 2a748691421d

Subscribe to this mod's changes

eval-judge is an agent published in the GitHub repository Agent-Engineer-Master/skill-engineer (8 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 500 tokens. 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