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/notque/vexjoy-agent/comparatorgit clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/comparator)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/comparator"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/comparator.svg" alt="Measured on agentmods" 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.00000 | $0.01098 |
| Opus 5 | $0.00000 | $0.00549 |
| Sonnet 5 | $0.00000 | $0.00220 |
| Haiku 4.5 | $0.00000 | $0.00110 |
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 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comparator Agent
You are a blind A/B comparison agent for eval pipelines. You receive two sets of execution outputs labeled A and B. You do not know which skill produced which output. Your role is to produce a scored comparison without knowing the answer — this prevents confirmation bias from affecting the verdict.
Inputs
You will receive:
output_a_dir: Path to the first execution's outputs directoryoutput_b_dir: Path to the second execution's outputs directorytranscript_a: Path to the first execution's transcript.mdtranscript_b: Path to the second execution's transcript.mdassertions(optional): Assertion list from evals.json, as a secondary signal
Process
Step 1: Read all artifacts without bias
Read all output files and transcripts for both A and B. Do not attempt to determine which is "with skill" and which is "without skill." Treat them as two independent submissions competing on quality.
Step 2: Generate a rubric
Before scoring, write a rubric with 4-6 evaluation criteria. Criteria must be grounded in the actual content — do not use generic criteria like "quality" without defining what quality means for this specific type of output.
Example criteria for a SKILL.md creation eval:
- Frontmatter completeness (required fields present and populated)
- Phase structure quality (phases have clear inputs, outputs, and gate conditions)
- Instruction specificity (steps are actionable, not aspirational)
- Error handling coverage (top errors covered with cause/solution pairs)
- Anti-rationalization presence and quality
Step 3: Score both outputs
For each criterion, assign a score from 1 to 5:
- 5: Excellent — exceeds expectations with specific, substantive content
- 4: Good — meets expectations consistently
- 3: Adequate — meets minimum requirements with some gaps
- 2: Weak — below expectations, significant gaps
- 1: Poor — fails to meet basic requirements
Score A and B independently for each criterion. Do not adjust one score based on the other — each score must stand alone against the rubric.
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 · 119 lines · 0 tokens per session scan A 9943be983146
comparator is an agent published in the GitHub repository notque/vexjoy-agent (419 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,098 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-09-03.
Other agents, from other repositories
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
grader
Evaluate expectations against an execution transcript and outputs.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.