agentleFS
ZelrayZelray/hermes-model-router/SKILL.md

model-router

Skill1 starsChanged 6 months agoMITView on GitHub

Intent-based model routing overlay for Hermes Agent. Use when a request should be mapped to a configured provider/model route such as image-prompt to Qwen 4B, debugging to Sonnet, cheap routine chat, or a user-defined route in skills.config.model-router.routes.

17 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 1 is distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do NOT copy this directory into ~/.claude/skills/ or any Claude skill path.

    line 8
  2. Very specific:

    Read ~/.hermes/config.yaml and inspect:

    line 21
  3. Very specific:

    If the table is absent, ask the user to add the sample from assets/config.yaml.routed.

    line 32
  4. Very specific:

    Prefer native auxiliary.* slots for built-in fixed tasks.

    line 36
  5. Very specific:

    Always state selected route, provider, model, rationale, fallback route, and exact command.

    line 47
  6. Distinctive:

    When terminal access is available, run:

    line 51
  7. Very specific:

    Use --execute only after the user confirms that an isolated hermes -z call is acceptable.

    line 57

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- IMPORTANT: This SKILL.md is a HERMES AGENT skill, NOT a Claude Code skill. Do NOT copy this directory into `~/.claude/skills/` or any Claude skill path. Copy this directory into the Hermes skills location on the machine running Hermes Agent (for example: `~/.hermes/skills/model-router/`). The surrounding `hermes-agent-specialist/` directory IS the Claude Code skill; this nested folder is one of its bundled assets that ships into Hermes. -->

Model Router for Hermes Agent

This Hermes skill adds intent-based model-routing guidance on top of stock Hermes. Hermes already supports auxiliary.*, delegation.*, fallback_model, custom providers, /model, and per-run --provider --model overrides. This skill does not add a Hermes core feature; it reads user-editable route settings from skills.config.model-router and returns the safest command or session-switch recommendation.

Load the routing table

Read ~/.hermes/config.yaml and inspect:

skills:
  config:
    model-router:
      default_route: routine_chat
      execution_mode: advise_or_oneshot
      routes: {}

If the table is absent, ask the user to add the sample from assets/config.yaml.routed. Do not invent a root intent_routes: key.

Route selection policy

Prefer native auxiliary.* slots for built-in fixed tasks. Use this skill only for semantic user intent. Match the user request against each route's keywords and intent. If multiple routes match, prefer the more specific and higher-capability route. If no route matches, use default_route.

Execution policy

command_modeBehavior
oneshotBuild an isolated hermes -z "..." --provider <provider> --model <model> command.
adviseRecommend the exact /model provider:model or hermes chat --provider ... --model ... -q ... command.
delegateUse Hermes delegation only when the task can be isolated as a subtask and the configured delegate model is appropriate.
current_sessionStay on the current/default session model.

Always state selected route, provider, model, rationale, fallback route, and exact command. Never use /model ... --global unless the user explicitly asks to persist the change.

Optional helper

When terminal access is available, run:

python scripts/model_router.py --prompt "<user request>" --config ~/.hermes/config.yaml

Use --execute only after the user confirms that an isolated hermes -z call is acceptable.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.