All plugins

modelscout

Per-task model choice from the models you actually have, so light work stops spending frontier-model tokens and subscription usage limits last longer. A pre_llm_call hook shows a short card for each new task (tier, best-fit model from your keys, subscriptions and live models.dev pricing, and why), then routes the work to a right-sized delegate_task child, up or down tier, asks, or stays, per your defaults. Bundles the modelscout skill and a /modelscout command for settings and a measured savings report. Disclosure — reads and writes ~/.claude/modelscout-profile.json (settings shared with ModelScout on other agents), appends routed-child outcomes (tier, model, status; no goal text) to ~/.claude/modelscout-outcomes.jsonl, and reads the model inventory and catalog JSON beside it plus Hermes's own models_dev_cache.json; it opens Hermes state.db read-only to look up a routed child's model and for the savings report, which also reads Claude Code transcripts read-only. A pre_llm_call hook adds routing instructions to each new task's prompt and can steer work into delegated subagents. In Hermes the plugin code makes no network calls and reads no credentials. On Claude Code, Codex, Gemini CLI and Grok Build (not Hermes), hooks/session_start.py runs scripts/catalog.py in a detached process to fetch the public models.dev catalog weekly, sending no keys or user data (modelscout: catalog off disables it). The bundled skill's optional discover-models.sh, run through the terminal tool, reads provider API-key env vars (and only checks whether Azure, Bedrock or Vertex credentials are present, without reading or using them), sends each only to its own provider's list-models endpoint and fetches the public models.dev catalog. Typing modelscout: grok setup (in any host, Hermes included) writes Grok Build's rules file ~/.grok/rules/modelscout.md (or under GROK_HOME) and reads ~/.grok/config.toml for custom model names; later ModelScout settings commands rewrite that file only if ModelScout wrote it, and modelscout: grok remove deletes it. No telemetry or self-updating, and no background processes in Hermes.

iknowterry1Modelsv0.3.11Updated 5 days ago

About

Per-task model choice from the models you actually have, so light work stops spending frontier-model tokens and subscription usage limits last longer. A pre_llm_call hook shows a short card for each new task (tier, best-fit model from your keys, subscriptions and live models.dev pricing, and why), then routes the work to a right-sized delegate_task child, up or down tier, asks, or stays, per your defaults. Bundles the modelscout skill and a /modelscout command for settings and a measured savings report. Disclosure — reads and writes ~/.claude/modelscout-profile.json (settings shared with ModelScout on other agents), appends routed-child outcomes (tier, model, status; no goal text) to ~/.claude/modelscout-outcomes.jsonl, and reads the model inventory and catalog JSON beside it plus Hermes's own models_dev_cache.json; it opens Hermes state.db read-only to look up a routed child's model and for the savings report, which also reads Claude Code transcripts read-only. A pre_llm_call hook adds routing instructions to each new task's prompt and can steer work into delegated subagents. In Hermes the plugin code makes no network calls and reads no credentials. On Claude Code, Codex, Gemini CLI and Grok Build (not Hermes), hooks/session_start.py runs scripts/catalog.py in a detached process to fetch the public models.dev catalog weekly, sending no keys or user data (modelscout: catalog off disables it). The bundled skill's optional discover-models.sh, run through the terminal tool, reads provider API-key env vars (and only checks whether Azure, Bedrock or Vertex credentials are present, without reading or using them), sends each only to its own provider's list-models endpoint and fetches the public models.dev catalog. Typing modelscout: grok setup (in any host, Hermes included) writes Grok Build's rules file ~/.grok/rules/modelscout.md (or under GROK_HOME) and reads ~/.grok/config.toml for custom model names; later ModelScout settings commands rewrite that file only if ModelScout wrote it, and modelscout: grok remove deletes it. No telemetry or self-updating, and no background processes in Hermes.

ModelScout

ModelScout knows which AI models you actually have, picks the right one for each task, and proves what that saved. Light work stops spending frontier-model tokens, so API costs drop and subscription usage limits last longer. It is the same open package across Hermes Agent, Claude Code, Codex, ChatGPT desktop and Gemini CLI. Full docs: github.com/iknowterry/modelscout.

Install

Hermes Agent:

hermes plugins install modelscout --enable

Claude Code:

claude plugin marketplace add iknowterry/modelscout && claude plugin install modelscout@modelscout

Codex / ChatGPT desktop:

codex plugin marketplace add iknowterry/modelscout && codex plugin add modelscout@modelscout

What it does in Hermes

For each new, substantial prompt, ModelScout first shows a short card:

🔭 ModelScout T1 mechanical · rename a field across 40 files
Best fit: claude-haiku-4.5 — pattern edits need no deep reasoning · ~1/5 of the current model's cost
→ ⚡ Delegating to a light-model subagent

Then it acts on your default for that tier:

  • switch: hands the task to delegate_task, which needs a model_map route for that model, for example from advanced-delegation. Routing works up-tier too: a hard task in an economy-model session goes to a stronger model.
  • ask: shows numbered choices and waits for your answer.
  • stay: does the work on the current model.

Follow-ups ("yes, test it"), quick questions and chit-chat get no card.

Picks come from the models your own keys and subscriptions reach, priced live from the models.dev catalog. On Hermes that catalog is Hermes's own models_dev_cache.json, which Hermes keeps fresh, so new models appear without a plugin update or a manual refresh. It never suggests a model you can't use.

What the plugin registers

SurfaceWhat it does
pre_llm_call hookAdds the card instructions to new, substantial prompts. Answers modelscout: … settings commands itself, blocking the turn so it makes no model call.
subagent_start hookMarks delegated children, so a child never gets a card or re-routes the task it was given.
subagent_stop hookRecords how each ModelScout-routed child ended (tier, model from state.db, status). No goal text.
/modelscout commandstatus (settings and catalog age), savings, weak, outcomes, forget, refresh, auto, ask, inform, off, reset, and per-tier defaults such as T1 stay or T3 switch
modelscout:modelscout skillThe full recommendation logic: tiers, price bands, honesty rules, savings report

No tools, no middleware, no Python dependencies.

Settings

Type modelscout: <setting> in a prompt or /modelscout <setting>:

  • Modes: auto (route without asking), ask, inform (card only) and off.
  • Per-tier defaults: for example T1 switch, T3 stay. A per-tier default beats the mode.
  • Savings: savings prints the measured report. It counts delegated child sessions whose goal starts with ModelScout: (the card asks for ModelScout: <Tier> · <goal>), using their own token usage, cost-weighted, with every price named.
  • Outcomes: the subagent_stop hook records how each routed child ended: tier, model and status only, in ~/.claude/modelscout-outcomes.jsonl. weak marks the last finished one as a poor result, the only status that counts against a model. Failed and interrupted runs are recorded as neutral errors. outcomes lists them.
  • Learning: when a model's recent results for a tier are weak (at least 3 finished in 30 days, 40% or more weak), that tier is routed one step up until the weak results age out. forget clears it.

Disclosures

  • Files read and written: settings live in ~/.claude/modelscout-profile.json, which is shared with ModelScout on the other agents. Routed-child outcomes are appended to ~/.claude/modelscout-outcomes.jsonl (tier, model, status, time; no goal text). Model lists are read from ~/.claude/model-inventory.json, ~/.claude/model-catalog.json and Hermes's own $HERMES_HOME/models_dev_cache.json when present (read-only).
  • Savings report: reads Hermes's session database ($HERMES_HOME/state.db, default ~/.hermes/state.db) and Claude Code transcripts under ~/.claude/projects/. Both are opened read-only.
  • Network and credentials: in Hermes the plugin code makes no network calls and never reads credentials; /modelscout refresh only reports the age of Hermes's cache. The bundled skill can tell the agent to run skills/modelscout/scripts/discover-models.sh, which goes through Hermes's normal terminal-tool approval. That script reads ANTHROPIC_API_KEY, OPENAI_API_KEY, GEMINI_API_KEY/GOOGLE_API_KEY and OPENROUTER_API_KEY from the environment. It also checks whether Azure OpenAI, AWS Bedrock or Google Vertex AI credentials are present, but never reads their values or uses them; those providers get the catalog's model list. It sends each key only to its own provider's read-only "list models" endpoint and fetches the public models.dev catalog. Skip it and ModelScout uses the host's model lineup and the catalog.
  • Other hosts only: On Claude Code, Codex, Gemini CLI and Grok Build (not Hermes), hooks/session_start.py runs scripts/catalog.py in a detached process to fetch the public models.dev catalog weekly; no keys or user data are sent, and modelscout: catalog off disables it. Hermes does not load that hook.
  • Grok Build only: modelscout: grok setup writes ~/.grok/rules/modelscout.md. ModelScout rewrites it only if it wrote it, and modelscout: grok remove deletes it.
  • Not present: no telemetry, no background processes in Hermes, no self-updating, no runtime patches of Hermes.

License

MIT

README from the reviewed commit ef26de9; it updates when the author re-pins.

More by iknowterry

2 plugins by iknowterry in the catalog.

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section