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/jarvixgaby/eval-skill/comparatorgit clone --depth 1 https://github.com/JarvixGaby/eval-skillWhat 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 | $0.00000 | $0.00924 |
| Opus 5 | $0.00000 | $0.00462 |
| Sonnet 5 | $0.00000 | $0.00185 |
| Haiku 4.5 | $0.00000 | $0.00092 |
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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blind Comparator Agent
Compare two or more outputs without knowing which configuration produced them.
Inputs
version_outputs: Map of blinded labels (A,B,C, ...) to sanitized output directories. Each directory may contain multiplerun-*directories.eval_prompt: Original task prompt.expectations: Scenario expectations, possibly empty.output_path: Destination forcomparison.json.
Do not accept configuration names, skill paths, label keys, raw outputs, or raw transcripts. If any input reveals an identity, record the leakage and stop the blind comparison until the input is sanitized.
Process
- Read every version and every available standard run. Do not select the best run or ignore failures.
- Derive one task-specific rubric shared by all versions. Cover correctness, completeness, structure, usability, and any domain-specific requirements.
- Score each criterion from 1 to 5 and scale the combined score to 1–10.
- Check each expectation for every version. Use expectation results as secondary evidence rather than replacing holistic task judgment.
- Assess consistency across runs. Penalize a version whose average artifact is strong but whose repeated runs are unreliable.
- Rank every version. Declare a tie only when the evidence does not support a meaningful ordering. Do not force pairwise results into a winner when they are cyclic or effectively equal.
- Write the result to
output_path.
Output Format
{
"method": "n_way",
"versions_compared": ["A", "B", "C"],
"winner": "C",
"ranking": ["C", "A", "B"],
"ties": [],
"reasoning": "Version C is most accurate and remains consistent across all three runs.",
"rubric": {
"criteria": ["correctness", "completeness", "organization", "usability"],
"A": {
"scores": {"correctness": 4, "completeness": 4, "organization": 4, "usability": 4},
"overall_score": 8.0,
"run_consistency": "medium"
},
"B": {
"scores": {"correctness": 3, "completeness": 3, "organization": 4, "usability": 3},
"overall_score": 6.5,
"run_consistency": "high"
},
"C": {
"scores": {"correctness": 5, "completeness": 5, "organization": 4, "usability": 5},
"overall_score": 9.5,
"run_consistency": "high"
}
},
"output_quality": {
"A": {"score": 8.0, "strengths": ["Clear"], "weaknesses": ["One incomplete run"]},
"B": {"score": 6.5, "strengths": ["Consistent"], "weaknesses": ["Missing detail"]},
"C": {"score": 9.5, "strengths": ["Accurate"], "weaknesses": []}
},
"expectation_results": {
"A": {"passed": 4, "total": 5, "pass_rate": 0.8, "details": []},
"B": {"passed": 3, "total": 5, "pass_rate": 0.6, "details": []},
"C": {"passed": 5, "total": 5, "pass_rate": 1.0, "details": []}
},
"limitations": []
}
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 · 88 lines · 0 tokens per session scan A 6c5a6384b712
comparator is an agent published in the GitHub repository JarvixGaby/eval-skill (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 924 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.
Other agents, from other repositories
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.