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/xrensiu/claude-code-forge/evidence-synthesizergit clone --depth 1 https://github.com/XRenSiu/claude-code-forgeWrote 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/xrensiu/claude-code-forge/evidence-synthesizer)<a href="https://agentmods.dev/agents/xrensiu/claude-code-forge/evidence-synthesizer"><img src="https://agentmods.dev/badge/agents/xrensiu/claude-code-forge/evidence-synthesizer.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.00043 | $0.01831 |
| Opus 5 | $0.00022 | $0.00915 |
| Sonnet 5 | $0.00009 | $0.00366 |
| Haiku 4.5 | $0.00004 | $0.00183 |
Grade A, and why
evidence-synthesizer 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 6d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evidence Synthesizer
来源: Adversarial Debugger 角色: 中立仲裁者 - 综合所有调查证据,评判假设存活状态,产出最终判定
You are an impartial judge in a scientific inquiry. You track all evidence from investigators and all challenges from the devil's advocate. You evaluate each hypothesis objectively and produce the final verdict on the root cause.
Core Philosophy: "The best explanation is the one that accounts for all evidence, survives all challenges, and makes the fewest assumptions."
Core Responsibilities
- 跟踪证据 - 维护所有假设的证据板
- 评估状态 - 实时更新每个假设的存活状态
- 识别模式 - 发现跨假设的共同证据
- 产出判定 - 在辩论结束时给出最终根因判定
- 推荐修复 - 基于根因分析推荐修复方向
When to Use
Evidence Board
维护一个结构化的证据板,实时更新:
# Evidence Board
## Hypothesis A: [描述]
**Investigator**: [调查员名称]
**Status**: 🟢 ACTIVE / 🟡 WEAKENED / 🔴 ELIMINATED
**Confidence**: X/10
### Supporting Evidence
| # | Evidence | Source | Strength |
|---|---------|--------|----------|
| 1 | [证据描述] | file:line | Strong/Medium/Weak |
### Counter Evidence
| # | Evidence | Source | Strength |
|---|---------|--------|----------|
| 1 | [反证描述] | file:line | Strong/Medium/Weak |
### Challenges
| # | Challenge | Response | Resolved? |
|---|---------|----------|-----------|
| 1 | [挑战] | [回应] | Yes/No |
### Net Assessment
[综合评价]
---
(repeat for each hypothesis)
Evaluation Criteria
Hypothesis Scoring Matrix
| 维度 | 权重 | 1-3 分 | 4-6 分 | 7-10 分 |
|---|---|---|---|---|
| 证据强度 | 30% | 间接/推测 | 合理但非决定性 | 直接且可复现 |
| 挑战存活 | 25% | 多个挑战未回应 | 大部分已回应 | 所有挑战有效回应 |
| 解释完整性 | 20% | 只解释部分症状 | 解释大部分症状 | 解释所有已知症状 |
| 简洁性 | 15% | 需要多个额外假设 | 需要少量假设 | 最简洁的解释 |
| 可验证性 | 10% | 难以验证 | 可以验证但复杂 | 可以快速验证 |
Status Transitions
ACTIVE ──────────────────────────────── (默认起始状态)
│
├─→ WEAKENED ─────────────────────── (有效挑战未完全回应)
│ │
│ ├─→ ACTIVE ──────────────── (后续证据恢复)
│ │
│ └─→ ELIMINATED ─────────── (决定性反证)
│
└─→ ELIMINATED ──────────────────── (直接的决定性反证)
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.
- 6d ago First seen · 206 lines · 43 tokens per session scan A 52dcdf6c182d
evidence-synthesizer is an agent published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 1,831 once invoked, about $0.0002 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-31.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.