test
Skill0 starsChanged 10 months agoMITView on GitHub
Test a model's performance and optionally update recommendations. User runs /model-router:test [model_name] or /model-router:test If not provided, ask which model to test. If model_name not provided: Verify the model is accessible: - Claude models: Always available - GPT models: Check Codex CLI installed and authenticated - Gemini models: Check Gemini CLI installed and authenticated - Ollama models: Check Ollama running and model pulled If not available: If "Use prompts from your folders": After user provides folders, scan for suitable prompts:
179 other projects use a version of this.
Adopted by
Most recently taken up by
- tyrantpiper/travel-pwatheir own version, first seen Nov 8, 2026
- phuthuycoding/kanban-flowtheir own version, first seen Nov 8, 2026
- pche-broken-artist/forge-of-thoughttheir own version, first seen Nov 8, 2026
- PMDevSolutions/Flaviantheir own version, first seen Nov 8, 2026
- domengabrovsek/agent-configtheir own version, first seen Nov 8, 2026
- domengabrovsek/claudetheir own version, first seen Nov 8, 2026
Used with
Projects with it also use agent-context-isolation, agentica-infrastructure 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.
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
parcadeiSkillagentica-infrastructure
Reference guide for Agentica multi-agent infrastructure APIs
Also in 3 projects that use this
- +10 more from parcadei
Other versions179 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 179
- react/react★ 252ksame name
- facebook/react★ 252ksame name
- apache/skywalking★ 25ksame name
- livewire/livewire★ 24ksame name
- NVIDIA/TensorRT★ 13ksame name
- FalkorDB/FalkorDB★ 10ksame name
- FastLED/FastLED★ 7.5ksame name
- fleetdm/fleet★ 7.2ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
169 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
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 154 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Test a model's performance and optionally update recommendations.
- Distinctive: line 13
If not provided, ask which model to test.
- Distinctive: line 19
If model_name not provided:
- Distinctive: line 47
Verify the model is accessible:
- Distinctive: line 87
After user provides folders, scan for suitable prompts:
- Very specific: line 205
If user approves changes, update ~/.model-router/models.yaml:
- Very specific: line 230
If tracking is enabled, append to ~/.model-router/tracking.jsonl:
“Common” is measured: kept by at least 6 in 10 of the 154 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 Test
Test a model's performance and optionally update recommendations.
Trigger
User runs /model-router:test [model_name] or /model-router:test
Arguments
model_name(optional): Model to test (e.g.,gemini-3-pro,gpt-5.2,deepseek-r1-70b)
If not provided, ask which model to test.
Instructions
1. Select Model to Test
If model_name not provided:
Which model would you like to test?
Available models:
Claude:
• claude-opus-4.5
• claude-sonnet-4.5
• claude-haiku-4.5
ChatGPT (requires Codex CLI):
• gpt-5.2
• gpt-5.2-codex
Gemini (requires Gemini CLI):
• gemini-3-pro
• gemini-flash
Ollama (local):
• deepseek-r1-70b
• llama-3.3-70b
• qwen-2.5-32b
Enter model name:2. Check Model Availability
Verify the model is accessible:
- Claude models: Always available
- GPT models: Check Codex CLI installed and authenticated
- Gemini models: Check Gemini CLI installed and authenticated
- Ollama models: Check Ollama running and model pulled
If not available:
[model_name] is not available.
Reason: [Codex CLI not installed / Ollama not running / etc.]
Would you like to set it up? Run /model-router:configure cli3. Choose Test Prompts
How would you like to test [model_name]?
○ Standard test suite (5 built-in prompts)
○ Use prompts from your folders (recommended for personalized testing)
○ Custom prompt (enter your own)If "Use prompts from your folders":
I'll select 10 prompts from your project files.
Which folders should I look in?
(Enter paths, or press enter for current project)
Examples:
• . (current project)
• ~/code/my-project
• Multiple: ./src, ./tests
Folders to use:After user provides folders, scan for suitable prompts:
# Look for:
# - README files with questions
# - Test files with assertions
# - Code files with TODO comments
# - Documentation with examplesPresent found prompts:
Found 15 potential test prompts. Selected 10:
1. [prompt preview...] (from src/auth.ts)
2. [prompt preview...] (from README.md)
3. [prompt preview...] (from tests/api.test.ts)
...
Use these prompts?
○ Yes, run tests
○ No, let me pick different ones
○ Add more folders4. Run Tests
Testing [model_name]...
Running [N] test prompts:
1. [prompt_type]: [brief description]
⏳ Running...
✓ Completed (2.3s)
Quality: [Good/Acceptable/Poor] (based on response coherence)
2. [prompt_type]: [brief description]
⏳ Running...
✓ Completed (4.1s)
Quality: [Good/Acceptable/Poor]
... (continue for all prompts)For each test, use the appropriate method:
- Claude: Use Claude Code directly (Task tool)
- Codex:
codex exec -m [model] "[prompt]" - Gemini:
gemini -y -m [model] -p "[prompt]" - Ollama: HTTP POST to Ollama API
5. Show Results
Test Results for [model_name]
═══════════════════════════════════════════════════════════
Tests run: 10
Passed: 9
Failed: 1
Performance:
Average latency: 3.2s
Fastest: 1.8s (simple_edit prompt)
Slowest: 6.4s (reasoning prompt)
Quality breakdown:
Good: 7/10 (70%)
Acceptable: 2/10 (20%)
Poor: 1/10 (10%)
Task type performance:
✓ code_review: Strong (4/4 good)
✓ reasoning: Good (2/3 good)
⚠ simple_edits: Mixed (1/2 good)
✗ critical_code: Weak (0/1 good)
═══════════════════════════════════════════════════════════6. Offer Recommendation Updates
Based on results, suggest updates:
Based on testing, [model_name] performed well for:
• code_review (comparable to current best: claude-sonnet-4.5)
• reasoning (better than current runner_up for your prompts)
Current recommendations:
code_review:
best: claude-sonnet-4.5
runner_up: gpt-5.2
Suggested changes:
1. Add [model_name] as runner_up for code_review
2. Promote [model_name] to best for reasoning (replaces current)
Would you like to:
○ Apply all suggested changes
○ Review and choose which to apply
○ Keep recommendations unchanged
○ Run more tests firstIf "Review and choose":
Select changes to apply:
□ Add [model_name] as runner_up for code_review
Current: gpt-5.2 → New: [model_name]
□ Promote [model_name] to best for reasoning
Current: deepseek-r1-70b → New: [model_name]
(deepseek-r1-70b moves to runner_up)7. Apply Updates
If user approves changes, update ~/.model-router/models.yaml:
task_types:
code_review:
best: claude-sonnet-4.5
runner_up: [model_name] # Updated
budget: gemini-flashConfirm:
Recommendations updated!
Changes applied:
• code_review runner_up: gpt-5.2 → [model_name]
Your personalized recommendations are now saved.
Community defaults are preserved separately.
Run /model-router:recommend to see updated suggestions.8. Save Test Results (if tracking enabled)
If tracking is enabled, append to ~/.model-router/tracking.jsonl:
{"type":"test","ts":"...","model":"[model]","prompts":10,"passed":9,"avg_latency_ms":3200,"quality":{"good":7,"acceptable":2,"poor":1}}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.

