setup
Skill0 starsChanged 10 months agoMITView on GitHub
First-time setup wizard for Model Router. Detects your environment, configures subscriptions, and sets up routing preferences. User runs /model-router:setup or this is the first time using any model-router command. You are setting up Model Router for the user. Follow this flow: First, welcome the user and run environment detection: Run the detection script: Parse the results and summarize what was found. Ask about subscriptions using AskUserQuestion with multiSelect: For each subscription they have, check if the CLI is set up:
- Installs packages
191 other projects use a version of this.
Adopted by
Most recently taken up by
- hydra-db/hydradb-claude-codetheir own version, first seen Nov 8, 2026
- WALKERKILLER/Look-Tongji-Notestheir own version, first seen Nov 8, 2026
- steerlabs/opensteertheir own version, first seen Nov 8, 2026
- ansvisor/ansvisortheir own version, first seen Nov 8, 2026
- dsifry/metaswarmtheir own version, first seen Nov 8, 2026
- anombyte93/prd-taskmastertheir own version, first seen Nov 8, 2026
Used with
Projects with it also use add-voice-transcription, add-discord and 10 more.
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.
juancruzmunozalbeloSkilladd-voice-transcription
Add voice message transcription to NanoClaw using OpenAI's Whisper API. Automatically transcribes WhatsApp voice notes so the agent can read and respond to them.
Also in 5 projects that use this
MicrosoftSkilladd-discord
Add Discord bot channel integration via Chat SDK.
Also in 11 projects that use this
MicrosoftSkilladd-slack
Add Slack channel integration via Chat SDK.
Also in 11 projects that use this
juancruzmunozalbeloSkilladd-telegram-swarm
Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".
Also in 7 projects that use this
- +8 more from microsoft
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- anthropics/knowledge-work-plugins★ 35ksame name
- garrytan/gbrain★ 32ksame name
- gavrielc/nanoclaw★ 31ksame name
- nanocoai/nanoclaw★ 31ksame name
- qwibitai/nanoclaw★ 31ksame name
- Q00/ouroboros★ 6.3ksame name
- pytorch/executorch★ 5.2ksame name
- agenticnotetaking/arscontexta★ 3.5ksame name
- aws/agent-toolkit-for-aws★ 3.4ksame name
- spotify/portal-ai-plugins★ 2.8ksame name
181 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 171 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Run the detection script:
- Distinctive: line 37
Ask about subscriptions using AskUserQuestion with multiSelect:
- Distinctive: line 63
If yes, guide them:
- Distinctive: line 173
Create the config directory and file:
“Common” is measured: kept by at least 6 in 10 of the 171 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.
Files
Model Router Setup
First-time setup wizard for Model Router. Detects your environment, configures subscriptions, and sets up routing preferences.
Trigger
User runs /model-router:setup or this is the first time using any model-router command.
Instructions
You are setting up Model Router for the user. Follow this flow:
1. Welcome and Detect Environment
First, welcome the user and run environment detection:
Welcome to Model Router! Let's get you set up.
This tool helps you route tasks to the best AI model based on:
- What you're trying to do (code review, reasoning, simple edits)
- What subscriptions and tools you have available
- Your preferences (quality vs cost)
Let me check what you have installed...Run the detection script:
python3 "$(dirname "$0")/../../scripts/detect_environment.py" --jsonParse the results and summarize what was found.
2. Subscriptions Question
Ask about subscriptions using AskUserQuestion with multiSelect:
Which AI subscriptions do you have?
□ Claude Pro ($20/mo) - You're using Claude Code, so likely yes
□ ChatGPT Plus ($20/mo) - Includes Codex CLI for GPT-5.2
□ Google AI Pro ($20/mo) - Includes Gemini CLI
□ None / API-only usage3. CLI Tools Setup
For each subscription they have, check if the CLI is set up:
If they have ChatGPT Plus but Codex CLI not detected:
You have ChatGPT Plus but Codex CLI isn't set up yet.
Codex CLI lets you use GPT-5.2 from the terminal - included with your subscription.
Would you like to set it up now?
○ Yes, walk me through it
○ No, skip for nowIf yes, guide them:
Let's set up Codex CLI:
1. Install: npm install -g @openai/codex
2. Authenticate: codex auth
3. This will open your browser for OAuth login
[Run the install command for them]
[Test the connection: codex exec -m gpt-5.2 "say test"]Same flow for Gemini CLI if they have Google AI Pro.
4. Local Models (Ollama)
Based on detection results:
If Ollama detected with models:
I detected Ollama running with these models:
- llama3.3:70b
- deepseek-r1:70b
These are free local models - great for saving on API costs!
Would you like to include them in routing?
○ Yes, use local models when appropriate [RECOMMENDED]
○ No, only use cloud modelsIf Ollama detected but no large models:
You have Ollama but only small models (7B).
For better quality, you could pull larger models:
- deepseek-r1:70b (best for reasoning, needs ~42GB RAM)
- llama3.3:70b (great all-rounder, needs ~42GB RAM)
Your system has [X]GB RAM.
Would you like to:
○ Pull deepseek-r1:70b now (recommended for your RAM)
○ Pull llama3.3:70b now
○ Skip for nowIf no Ollama and system has 32GB+ RAM:
Your system has [X]GB RAM - enough to run local AI models for free!
Ollama lets you run models like Llama 3.3 70B locally.
Would you like to:
○ Set up Ollama now (recommended)
○ Skip local modelsIf no Ollama and insufficient RAM:
Local models require 16GB+ RAM. Your system has [X]GB.
Do you have another machine that could run Ollama?
○ Yes, enter the host address
○ No, skip local models5. Routing Preference
When routing tasks, which services should we try FIRST?
(To preserve your Claude usage for complex tasks)
○ ChatGPT + Gemini first (preserve Claude) [RECOMMENDED]
Use GPT-5.2 and Gemini for routine work, save Claude for complex tasks
○ Claude first (best quality)
Always use Claude when available, uses subscription faster
○ Cheapest first (maximize free/local)
Use Ollama and Gemini Flash whenever possible
○ Ask me each time
Show recommendation and let me choose6. Profile Selection
Choose your default routing profile:
○ Quality - Always use the best model for the task
○ Balanced - Smart routing based on task complexity [DEFAULT]
○ Budget - Maximize cheap/free models
○ Local-only - Only use Ollama, never cloud7. Tracking Preferences
Would you like to enable usage tracking?
This helps Model Router learn which models work best for you.
○ No tracking [DEFAULT]
○ Yes, basic - Task type, model used, success/fail
○ Yes, detailed - Include quality ratings and timing8. Write Configuration
Create the config directory and file:
mkdir -p ~/.model-routerWrite ~/.model-router/config.yaml:
version: "1.0"
created_at: [timestamp]
subscriptions:
claude_pro: true/false
chatgpt_plus: true/false
google_ai_pro: true/false
cli_tools:
codex:
installed: true/false
path: /path/to/codex
gemini:
installed: true/false
path: /path/to/gemini
ollama:
enabled: true/false
host: localhost
port: 11434
models:
- llama3.3:70b
- deepseek-r1:70b
preferences:
routing: preserve_claude | quality_first | budget_first | ask_each_time
profile: quality | balanced | budget | local_only
tracking:
enabled: true/false
level: none | basic | detailedCopy the default models.yaml to user's config:
cp "$(dirname "$0")/../../data/models.yaml" ~/.model-router/models.yaml9. Summary
Show a summary of the setup:
Setup complete! Here's your configuration:
┌─ Model Router Configuration ─────────────────────────────┐
│ │
│ Subscriptions: │
│ ✓ Claude Pro ✓ ChatGPT Plus ✓ Google AI Pro │
│ │
│ CLI Tools: │
│ ✓ Codex CLI (GPT-5.2) │
│ ✓ Gemini CLI │
│ │
│ Local Models (Ollama): │
│ ✓ llama3.3:70b │
│ ✓ deepseek-r1:70b │
│ │
│ Routing: ChatGPT + Gemini first (preserve Claude) │
│ Profile: Balanced │
│ Tracking: Disabled │
│ │
├──────────────────────────────────────────────────────────┤
│ │
│ Quick commands: │
│ /model-router:help - See all commands │
│ /model-router:recommend - Get model recommendation │
│ /model-router:status - Check current config │
│ /model-router:configure - Change settings │
│ │
└──────────────────────────────────────────────────────────┘
You're all set! Model Router will now help you choose the best
model for each task based on your setup.Files Referenced
scripts/detect_environment.py- Environment detectiondata/models.yaml- Default model recommendations~/.model-router/config.yaml- User configuration (created)~/.model-router/models.yaml- User's model recommendations (copied)
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
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.

