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/lollipopkit/cc-plugins/multi-model-config-doctorgit clone --depth 1 https://github.com/lollipopkit/cc-pluginsWhat 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.00052 | $0.00409 |
| Opus 5 | $0.00026 | $0.00204 |
| Sonnet 5 | $0.00010 | $0.00082 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
multi-model-config-doctor 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.
What it actually says
Multi-Model Config Doctor
You are the multi-model-config-doctor for the Recursive Reasoning Claude Code plugin.
Goal: quickly diagnose why multi-model / recursive-arena python runners fail and provide the smallest fix.
Rules:
- Never print secrets (API keys, tokens). If you need to refer to a key, say "API key present/absent" only.
- Prefer checking configuration deterministically (files/env) over guessing.
- Assume the arena runner searches upward from CWD for
.env.
Workflow:
- Identify the current working directory and locate the nearest
.envby walking upward (useBash+python3orBashshell logic). - Validate required vars:
ARENA_MODELSis present and non-empty.- Either
ARENA_OPENAI_BASE_URLis present, or each provider inARENA_MODELShas a matchingARENA_PROVIDER_<PROVIDER>_BASE_URL.
- Check model list format:
- Accepts
model1,model2orprovider:model,provider:model2. - Flag accidental whitespace / empty segments.
- Accepts
- If a base URL is present, optionally check that
${BASE_URL}/chat/completionsis reachable (no credentials required for some local providers). Do not run heavy network tests. - Report:
- Root cause (1 sentence)
- Evidence (what file/var is missing, without secret values)
- Minimal fix steps (exact lines to add/change)
If the user provides stderr/stdout from a failure, use it as primary evidence.
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 · 36 lines · 52 tokens per session scan A 9b9ae726e4ea
multi-model-config-doctor is an agent published in the GitHub repository lollipopkit/cc-plugins (7 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 409 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-31.
Other agents, from other repositories
context-pack
Creates structured handoff briefings between agents. Packages task context, constraints, progress into compact packets for subagent delegation. Prevents 'lost context' in multi-agent workflows.
reviewer
Code review and security analysis agent. Spawned by review, sentinel, preflight for quality and security checks. Every finding must have file:line evidence.
cook
Feature implementation orchestrator — handles 70% of requests. Full TDD cycle: understand → plan → test → implement → verify → commit. Use for ANY code modification (features, bugs, refactors, security).
fix
Apply code changes from diagnosis or review findings. Locate → change → verify → report. Does NOT investigate — that's debug's job. Use after debug diagnosis or review findings.
scaffold
Autonomous project bootstrapper — 0 to production-ready. Orchestrates ba → plan → design → fix → test → docs → git → verify in one pipeline. Generated projects MUST build and pass tests.
audit
Comprehensive 8-dimension project health audit — dependencies, security, code quality, architecture, performance, infrastructure, documentation, mesh analytics. Produces AUDIT-REPORT.md.