agentleFS
mikemorgensternmikemorgenstern/model-router/skills/configure/SKILL.md

configure

Skill0 starsChanged 10 months agoMITView on GitHub

Change Model Router settings. User runs /model-router:configure or /model-router:configure [setting] If not provided, show menu of options. Read ~/.model-router/config.yaml If doesn't exist: Subscriptions: Update config and offer to set up missing CLI tools. Routing Preference: If enabling, explain: If pulling models, guide through ollama pull [model]. Walk through installation/auth as in setup skill. After any change, update ~/.model-router/config.yaml: If user chooses reset: If yes, delete config and run /model-router:setup.

43 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use calendar and build.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • jacobraskSkill

    calendar

    Interact with Apple Calendar via AppleScript. Use when the user asks to check calendar, view events, create events, manage schedule, find free time, or list calendars. Triggers include "my calendar", "my schedule", "calendar events", "create event", "add to calendar", "what's on my calendar", "free time", "available slots", "upcoming events", "today's events". Requires macOS with Calendar.app.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    build

    Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 43 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If not provided, show menu of options.

    line 19
  2. Distinctive:

    If doesn't exist:

    line 27
  3. Distinctive:

    Update config and offer to set up missing CLI tools.

    line 68
  4. Very specific:

    If pulling models, guide through ollama pull [model].

    line 123
  5. Very specific:

    After any change, update ~/.model-router/config.yaml:

    line 141
  6. Distinctive:

    If user chooses reset:

    line 160
  7. Very specific:

    If yes, delete config and run /model-router:setup.

    line 171

“Common” is measured: kept by at least 6 in 10 of the 43 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

Model Router Configure

Change Model Router settings.

Trigger

User runs /model-router:configure or /model-router:configure [setting]

Arguments

  • setting (optional): Specific setting to change. One of:
    • subscriptions - Update subscription status
    • routing - Change routing preference
    • profile - Change profile
    • tracking - Enable/disable tracking
    • ollama - Configure Ollama
    • cli - Set up CLI tools

If not provided, show menu of options.

Instructions

1. Load Current Configuration

Read ~/.model-router/config.yaml

If doesn't exist:

No configuration found. Run /model-router:setup for initial setup.

2. Show Configuration Menu (if no argument)

What would you like to configure?

1. Subscriptions - Update which subscriptions you have
2. Routing preference - Change how models are prioritized
3. Profile - Switch between quality/balanced/budget/local
4. Tracking - Enable or disable usage tracking
5. Ollama - Configure local models
6. CLI tools - Set up Codex or Gemini CLI
7. Reset - Start fresh with setup wizard

Current settings:
  Profile: [current]
  Routing: [current]
  Tracking: [current]

Enter number or setting name:

3. Handle Each Setting

Subscriptions:

Current subscriptions:
  Claude Pro:    [✓/✗]
  ChatGPT Plus:  [✓/✗]
  Google AI Pro: [✓/✗]

Which would you like to change?
□ Claude Pro ($20/mo)
□ ChatGPT Plus ($20/mo)
□ Google AI Pro ($20/mo)

Update config and offer to set up missing CLI tools.

Routing Preference:

Current: [preserve_claude/quality_first/budget_first/ask_each_time]

Choose routing preference:
○ ChatGPT + Gemini first (preserve Claude)
○ Claude first (best quality)
○ Cheapest first (maximize free/local)
○ Ask me each time

Profile:

Current: [quality/balanced/budget/local_only]

Choose profile:
○ Quality - Always use the best model
○ Balanced - Smart routing based on complexity
○ Budget - Maximize cheap/free models
○ Local-only - Only use Ollama

Tracking:

Current: [disabled/basic/detailed]

Choose tracking level:
○ Disabled - No tracking
○ Basic - Task type, model, success/fail
○ Detailed - Include quality ratings and timing

If enabling, explain:

Tracking helps Model Router learn which models work best for you.
Data is stored locally at ~/.model-router/tracking.jsonl
Run /model-router:learn to analyze patterns.

Ollama:

Current Ollama config:
  Enabled: [yes/no]
  Host: [localhost:11434 or custom]
  Models: [list]

What would you like to do?
○ Enable/disable Ollama
○ Change host address
○ Pull new models
○ Remove models from routing

If pulling models, guide through ollama pull [model].

CLI Tools:

CLI Tool Status:
  Codex: [✓ Ready / ⚠ Not auth / ✗ Missing]
  Gemini: [✓ Ready / ⚠ Not auth / ✗ Missing]

What would you like to do?
○ Set up Codex CLI (for ChatGPT Plus)
○ Set up Gemini CLI (for Google AI Pro)
○ Re-authenticate existing CLI

Walk through installation/auth as in setup skill.

4. Save Configuration

After any change, update ~/.model-router/config.yaml:

# Updated field
preferences:
  routing: [new_value]

Confirm:

Configuration updated.

Changed: [setting] → [new_value]

Run /model-router:status to see full configuration.

5. Reset Option

If user chooses reset:

This will delete your current configuration and run setup again.

Your tracking data (if any) will be preserved.

Continue?
○ Yes, reset configuration
○ No, cancel

If yes, delete config and run /model-router:setup.

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.