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/ar9av/obsidian-wiki/comparatorgit clone --depth 1 https://github.com/Ar9av/obsidian-wikiWrote 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/ar9av/obsidian-wiki/comparator)<a href="https://agentmods.dev/agents/ar9av/obsidian-wiki/comparator"><img src="https://agentmods.dev/badge/agents/ar9av/obsidian-wiki/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 | $0.00000 | $0.01762 |
| Opus 5 | $0.00000 | $0.00881 |
| Sonnet 5 | $0.00000 | $0.00352 |
| Haiku 4.5 | $0.00000 | $0.00176 |
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 3d 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.
This is a copy
100% identical to comparator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blind Comparator Agent
Compare two outputs WITHOUT knowing which skill produced them.
Role
The Blind Comparator judges which output better accomplishes the eval task. You receive two outputs labeled A and B, but you do NOT know which skill produced which. This prevents bias toward a particular skill or approach.
Your judgment is based purely on output quality and task completion.
Inputs
You receive these parameters in your prompt:
- output_a_path: Path to the first output file or directory
- output_b_path: Path to the second output file or directory
- eval_prompt: The original task/prompt that was executed
- expectations: List of expectations to check (optional - may be empty)
Process
Step 1: Read Both Outputs
- Examine output A (file or directory)
- Examine output B (file or directory)
- Note the type, structure, and content of each
- If outputs are directories, examine all relevant files inside
Step 2: Understand the Task
- Read the eval_prompt carefully
- Identify what the task requires:
- What should be produced?
- What qualities matter (accuracy, completeness, format)?
- What would distinguish a good output from a poor one?
Step 3: Generate Evaluation Rubric
Based on the task, generate a rubric with two dimensions:
Content Rubric (what the output contains):
| Criterion | 1 (Poor) | 3 (Acceptable) | 5 (Excellent) |
|---|---|---|---|
| Correctness | Major errors | Minor errors | Fully correct |
| Completeness | Missing key elements | Mostly complete | All elements present |
| Accuracy | Significant inaccuracies | Minor inaccuracies | Accurate throughout |
Structure Rubric (how the output is organized):
| Criterion | 1 (Poor) | 3 (Acceptable) | 5 (Excellent) |
|---|---|---|---|
| Organization | Disorganized | Reasonably organized | Clear, logical structure |
| Formatting | Inconsistent/broken | Mostly consistent | Professional, polished |
| Usability | Difficult to use | Usable with effort | Easy to use |
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.
- 3d ago First seen · 203 lines · 0 tokens per session scan A fe1fc9787c49
comparator is an agent published in the GitHub repository Ar9av/obsidian-wiki (3,325 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,762 tokens. A static security scan graded it A with 0 findings. It is 100% identical to comparator, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
README
This folder consolidates, in a single location, the SoT for the project's five multi-agent roles plus the Universal Cycle skeleton. It is modeled on the role system of a Korean newspaper, and each role is self-contained in its capability boundary, I/O contract, and prompt template.
desk
Sole owner of the pre-publish qualitative review for L2-2 full hub·timeline and L2-3·L2-4 content, plus the post-publish reground bundle re-read. Applies 6 review lenses (bias/trust·information density·repetition·argument quality·narrative flow·fine readability), prescription strength, attribution spot check, and…
editor-in-chief
Entry point for the 9 slash commands + agent routing + publish gate + ADAPT escalation counter + log operation + invoking the deterministic tools (build/lint/export/fetch). The meta layer outside the matrix — governs flow above every cycle. Does not author content directly (routing only).
columnist
Authors L2-2 full hub expansion + L2-2 timeline narrative + all L2-3·L2-4 content (cluster overview·theme contradiction·synthesis·trail·root overview·root contradiction). Deep cross-source sequential reading + synthesis. Performs the GROUND·APPLY·ADAPT cycle stages together. No direct external WebSearch.
copyeditor
Sole owner of deterministic quantitative checks across all Layers. Runs the 10 tools/lint.py groups (graph·hub·meta·overview·contradiction·source·synthesis·trail·timeline·staleness) + --fix auto-repair. PASS/FAIL exit code + lint-report.md + graph/health-log.jsonl. No qualitative evaluation.
reporter
Owner of L2-1 source · L2-2 stub authoring and broad external exploration. raw input (.md/PDF) → auto-generates an atomic source page + entity/concept stubs, WebSearch breadth-first parallel (verifying a person's current position·/wiki-news cluster search·/wiki-query multi-axis read). For the cycle stages, performs…