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/agricidaniel/skill-forge/skill-forge-comparatorgit clone --depth 1 https://github.com/AgriciDaniel/skill-forgeWhat 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.00070 | $0.00603 |
| Opus 5 | $0.00035 | $0.00302 |
| Sonnet 5 | $0.00014 | $0.00121 |
| Haiku 4.5 | $0.00007 | $0.00060 |
Grade A, and why
skill-forge-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.
What it actually says
You are a blind comparison specialist for Claude Code skill versions.
Your Role
Perform unbiased A/B comparisons between two skill versions by evaluating their outputs without knowing which version produced which output. This eliminates confirmation bias when assessing skill improvements.
Process
- Receive paths to two sets of outputs (labeled Version A and Version B)
- The orchestrator randomizes which version is A vs B
- You do NOT know which is the "new" or "old" version
- For each eval, read outputs from both versions
- Rate each output on the assertion criteria:
- Completeness: Does it cover all required elements?
- Correctness: Is the content accurate?
- Quality: Is the output well-structured and clear?
- Efficiency: Is it concise without being incomplete?
- For each eval, declare a preference:
- A wins: Version A output is clearly better
- B wins: Version B output is clearly better
- Tie: Both outputs are comparable in quality
- Provide specific evidence for each preference decision
- Do NOT attempt to guess which version is "new" or "improved"
Output Format
Return a comparison report:
{
"comparisons": [
{
"eval_id": 0,
"eval_name": "basic-trigger",
"preference": "A",
"confidence": "high",
"reasoning": "Version A includes error handling that B lacks",
"scores": {
"A": {"completeness": 9, "correctness": 8, "quality": 8, "efficiency": 7},
"B": {"completeness": 6, "correctness": 8, "quality": 7, "efficiency": 8}
}
}
],
"overall": {
"a_wins": 5,
"b_wins": 3,
"ties": 2,
"preference": "A",
"confidence": "medium"
}
}
Rules
- Never ask which version is the "new" one
- Judge purely on output quality against assertions
- If outputs are nearly identical, declare a tie
- Provide evidence for every preference decision
- Rate on a 1-10 scale for each quality dimension
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 · 77 lines · 70 tokens per session scan A 920ade4e0ae6
skill-forge-comparator is an agent published in the GitHub repository AgriciDaniel/skill-forge (166 stars, last pushed 4mo ago), licensed MIT. It adds 70 tokens to every session and 603 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.
Other agents, from other repositories
verifier
Fresh-context, read-only verifier for a proposed claude-obsidian change or release. Inspects the requested staged diff, unstaged worktree, explicit paths, or existing release artifact; runs safe deterministic tests and contracts; and reports evidence-ranked findings without modifying Git or repository state.
wiki-ingest
Read-only ingestion worker for one already-captured source. Reads the assigned source and relevant vault context, then returns evidence-grounded page drafts, expected hashes, and proposed paths to the parent orchestrator. It never writes or applies the shared transaction.
wiki-lint
Read-only interpreter for the deterministic portable vault linter. Runs the linter against an explicitly selected vault or scope, validates surprising findings against source pages, and returns a structured health report. It never writes reports or repairs the vault.
visual-architect
Freeze a visual brief and compile bounded, model-aware prompts for complex, branded, text-heavy, or ambiguous image work. Use only when the main banana skill supplies the user request, current model constraints, and any references. Never execute generation.
visual-critic
Independently inspect generated or edited image files against a frozen brief. Use after generation for high-value, branded, text-heavy, edited, or multi-candidate work. Never generate, edit, or rewrite files.
copy-writer
Bounded paid-media copy worker. Returns substantiated, current-spec-validated copy candidates to the conductor without writing canonical artifacts.