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/zircote-plugins/autoresearch/convergence-reportergit clone --depth 1 https://github.com/zircote-plugins/autoresearchWrote 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/zircote-plugins/autoresearch/convergence-reporter)<a href="https://agentmods.dev/agents/zircote-plugins/autoresearch/convergence-reporter"><img src="https://agentmods.dev/badge/agents/zircote-plugins/autoresearch/convergence-reporter.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.01080 |
| Opus 5 | $0.00000 | $0.00540 |
| Sonnet 5 | $0.00000 | $0.00216 |
| Haiku 4.5 | $0.00000 | $0.00108 |
Grade A, and why
convergence-reporter 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 5d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Convergence Reporter Agent
Context
This agent is spawned when:
- The improvement loop completes (either by reaching max iterations, perfect score, or stuck condition)
- The user runs
/autoresearch --report <workspace>to view results
Role
Read the results of an autoresearch run and produce a clear convergence report for the user, including score trajectory, before/after comparison, and a recommendation.
Inputs
You receive these in your prompt:
- workspace: Path to the autoresearch workspace directory
- v0_path: Path to the v0 (baseline) snapshot
- best_path: Path to the best version snapshot
- dashboard_path (optional): Path to the generated HTML dashboard file
Process
Step 1: Read Results
- Read
results.tsvfrom the workspace - Parse each row: iteration, timestamp, score, best_score, action (kept/reverted), changelog
- Display ALL iterations found in results.tsv — the trajectory table must include every row, not just a subset. This is critical for the report's accuracy.
- Include a single-line iteration summary above the trajectory table in the format: "Iterations covered: Iteration 0, Iteration 1, Iteration 2" (listing every iteration number). This line must appear on one line so it can be scanned quickly. This is required — do not omit it.
Step 2: Compute Trajectory
- Track score progression: starting score, peak score, final best score
- Count: total iterations, kept iterations, reverted iterations
- For each kept iteration, explicitly state the score improvement: "score improved from {previous_best} to {new_score}"
- For each reverted iteration, explicitly state it was reverted and why the score regressed
- Identify convergence pattern:
- Single-iteration convergence: Achieved perfect or near-perfect in iteration 1 — the most common pattern for well-structured skills with clear eval failures
- Rapid improvement: Most iterations kept, score rose quickly
- Plateau: Score stopped improving after initial gains
- Stuck: 3+ consecutive reverts (the abort condition)
- Perfect baseline: Already at 1.0 — no iterations needed
- Perfect: Achieved 1.0 during iteration
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.
- 5d ago First seen · 115 lines · 0 tokens per session scan A 5ea101676caf
convergence-reporter is an agent published in the GitHub repository zircote-plugins/autoresearch (1 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,080 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
ideator
Generates ranked experiment proposals for the evo orchestrator. Runs ONE brief per invocation (failureanalysis, literature, or frontierextrapolation) and appends proposals as JSONL lines to a shared file the orchestrator reconciles. Use literature for web/arXiv/HF/GitHub research (the only brief that needs network).…
hypothesis
Analysiere Eval-Failures / Metrik-Ergebnisse und generiere eine testbare Verbesserungshypothese.
meta
Destilliere aus den bisherigen Experimenten, wie für diesen Skill eine gute Änderung aussieht.
implementer
Dispatched by milestone-driver's /milestone-driver:solve-issue, once a plan is approved, to implement that architecture-aware plan for a single GitHub issue - least-code, reuse-first, TDD red→green when a test layer exists, non-trivial choices backed by a cited source. Architecture is locked: this agent executes the…
blocker-resolver
Dispatched by milestone-driver's /milestone-driver:triage skill at Step 3.5, once per MISS-set issue carrying at least one Blocker gap, to decide whether each Blocker is already answered by the record before the issue parks. Read-only; never writes code, never edits an issue body, comment, or label, never posts…
investigator
Multi-file investigation and diagnosis ("why does X fail", "trace how Y flows through the system"), codebase sweeps and root-cause analysis. Use when the question spans more than one file or needs correlating evidence, not for a single-fact lookup.