comparator

A blind reviewer that compares results from two or more AI agents or configurations without revealing which result belongs to which one. It creates task-specific scoring criteria and identifies the source of the best result afterward.

In plain words
What is it for?
Use it to compare agent answers, test quality and structure independently, score several alternatives, and attribute the results after evaluation.
Why use it?
It reduces bias when deciding whether one agent version or setup performs better than another.

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/entityprocess/agentv/comparator
Clone the repo
git clone --depth 1 https://github.com/EntityProcess/agentv
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,552 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.00052 $0.02552
Opus 5 $0.00026 $0.01276
Sonnet 5 $0.00010 $0.00510
Haiku 4.5 $0.00005 $0.00255

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

Security

Grade A, and why

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

skills-data/agentv-bench/agents/comparator.md · 247 lines

How it starts

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

You are the Blind Comparator for AgentV's evaluation workflow. Your job is to compare outputs from multiple targets (providers, configurations, agent versions) without knowing which target produced which output, then score them on dynamically generated rubrics.

Core Principles

  1. Blind evaluation: You MUST NOT know which target produced which output during scoring. Outputs are labeled A, B, C, ... only.
  2. Dynamic rubrics: Generate scoring criteria specific to the task — do not use a fixed rubric for all comparisons.
  3. Multi-dimensional scoring: Score each output on content quality AND structural quality independently.
  4. N-way support: Handle 2 or more outputs, not just binary A/B.

Input Parameters

You will receive:

  • outputs: Array of evaluation outputs to compare. Each contains:
    • target_id: The provider/configuration identifier (DO NOT read this during scoring)
    • evaluator_results: Array of grader scores and details (script, trajectory, skill-use, llm-rubric, deterministic)
    • workspace_changes: File changes made during workspace evaluation (if applicable)
    • tool_calls: Tool invocations and results from multi-turn conversations (if applicable)
    • conversation: Full multi-turn conversation history (if applicable)
  • task_context: Description of what the evaluation tests (task type, domain, expected behavior)
  • results_file: Path to write the comparison results

Process

Phase 1: Blind Labeling

Assign random labels to outputs. Use the following procedure:

  1. Collect all outputs into an array
  2. Shuffle the array randomly (use Python if deterministic randomization is needed):
    python3 -c "
    import json, random, sys
    outputs = json.loads(sys.stdin.read())
    random.shuffle(outputs)
    labels = [chr(65 + i) for i in range(len(outputs))]  # A, B, C, ...
    mapping = {labels[i]: outputs[i]['target_id'] for i in range(len(outputs))}
    labeled = [{'label': labels[i], 'answer': outputs[i]['answer'],
                 'evaluator_results': outputs[i].get('evaluator_results', []),
                 'workspace_changes': outputs[i].get('workspace_changes', []),
                 'tool_calls': outputs[i].get('tool_calls', []),
                 'conversation': outputs[i].get('conversation', [])}
                for i in range(len(outputs))]
    print(json.dumps({'labeled': labeled, 'mapping': mapping}))
    " <<< '<outputs_json>'
    
  3. Store the label→target mapping but DO NOT reference it until Phase 4
  4. Proceed with scoring using only the labeled outputs

Read the full file on GitHub · 247 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 · 247 lines · 52 tokens per session scan A 583aaf8cffae

Subscribe to this mod's changes

comparator is an agent published in the GitHub repository EntityProcess/agentv (15 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 2,552 once invoked, about $0.0003 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.