Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/agentscope-ai/agentteams/model-switchnpx skills add agentscope-ai/AgentTeams --skill model-switchgit clone --depth 1 https://github.com/agentscope-ai/AgentTeamsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/agentscope-ai/agentteams/model-switch)<a href="https://agentmods.dev/skills/agentscope-ai/agentteams/model-switch"><img src="https://agentmods.dev/badge/skills/agentscope-ai/agentteams/model-switch.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00025 | $0.01044 |
| Opus 5 | $0.00013 | $0.00522 |
| Sonnet 5 | $0.00005 | $0.00209 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
model-switch scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Model Switch
Switch the Manager's own LLM model. The script tests connectivity first, then patches openclaw.json.
Usage
bash /opt/agentteams/agent/skills/model-switch/scripts/update-manager-model.sh <MODEL_ID> [--context-window <SIZE>] [--no-reasoning]
Examples:
bash /opt/agentteams/agent/skills/model-switch/scripts/update-manager-model.sh claude-sonnet-4-6
bash /opt/agentteams/agent/skills/model-switch/scripts/update-manager-model.sh my-custom-model --context-window 300000
bash /opt/agentteams/agent/skills/model-switch/scripts/update-manager-model.sh deepseek-chat --no-reasoning
What the script does
- Strips any
agentteams-gateway/prefix from the model name - Tests the model via
POST /v1/chat/completionson the AI Gateway — exits with error if unreachable - If the model is already in the
modelsarray: switchesagents.defaults.model.primary - If the model is new: adds it to the
modelsarray and switches primary - Always outputs
RESTART_REQUIRED
After running the script
The script always outputs RESTART_REQUIRED. Run openclaw gateway restart to apply the change, then tell the human admin the switch is complete.
Reasoning control
By default, reasoning (extended thinking) is enabled. To disable it, pass --no-reasoning.
On failure
If the gateway test fails (non-200), the script outputs ERROR: MODEL_NOT_REACHABLE and exits. No changes are made to openclaw.json.
When you see this error, tell the human admin clearly:
- The model is not reachable because the current default AI Provider likely does not support it.
- They need to open the Higress Console and:
- Create a new AI Provider for the model's vendor (e.g.
kimi,deepseek,minimax). - Create a new AI Route with a model name prefix predicate (e.g. provider
kimi→ matchkimi-*), so that requests for models with that prefix are routed to the new provider, while unmatched models continue to go through the default route.
- Create a new AI Provider for the model's vendor (e.g.
- Do NOT modify the default AI Provider — it is managed by the initialization config and will be overwritten on restart.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 83 lines · 25 tokens per session scan A c1cc5460084b
model-switch is a skill published in the GitHub repository agentscope-ai/AgentTeams (5,552 stars, last pushed yesterday), licensed Apache-2.0. It adds 25 tokens to every session and 1,044 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
plan-ceo-review
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when…
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, and create a PR. Use for an explicit /ship invocation or when the user requests the full ship, release, or deploy workflow. For an ordinary commit, push, or pull-request publishing request, use the built-in…
design-review
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use…
plan-eng-review
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when…
autoplan
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when…
retro
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively…