Openclaw Tokenapi Qiehuan Skills

提供基于WebUI的快速AI模型切换工具，支持保存配置、一键切换、批量导入及API Key本地存储管理。

Security Scan

The package generally implements a local WebUI model-switcher, but the documentation and code disagree about how API keys are handled and the backend can write sensitive files and run system commands — review before installing.

Purpose & Capability

The skill's name/description (model switcher + local API Key memory) matches the included frontend and backend code. However SKILL.md states "API Key 仅保存在浏览器 localStorage（本地），不上传到任何服务器" and claims the backend only reads/writes openclaw.json (non-API parts). The backend code (routes and ConfigManager) clearly accepts API keys via API endpoints and calls secure_config.update/save and update_auth_profile — i.e., it persists API keys to disk/agent auth-profiles. That mismatch between README and implementation is a substantive inconsistency.

Instruction Scope

Runtime instructions tell the agent to start a local backend and modify ~/.openclaw/openclaw.json and auth-profiles files. The code implements endpoints that write configs and API keys, and a GatewayController that runs system commands (taskkill, spawn gateway.cmd, launch a restart .bat). Those actions go beyond simple in-memory switching: they modify user files and control local processes. That scope is plausible for a gateway manager, but it's sensitive and should be explicit to the user.

Install Mechanism

No remote download/install spec is included; the package is local code + static frontend and a pip requirements file. No external arbitrary URL downloads or extract operations were detected. Risk from installation is limited to installing Python dependencies and running the included code.

Credentials

The skill requests no declared environment variables, but it will accept and persist provider API keys via HTTP endpoints and write to user config paths (e.g., ~/.openclaw/openclaw.json and ~/.openclaw/agents/main/agent/auth-profiles.json). Whether keys are encrypted at rest depends on secure_config.py (not shown in the truncated listing). The backend also enables permissive CORS (allow_origins=['*']) which could expose the local API if the server is not strictly bound to localhost — this amplifies risk for stored credentials.

Persistence & Privilege

The skill is not always-enabled and is user-invocable. It does request ability to modify local OpenClaw files and to start/stop local processes via subprocess calls. Autonomous invocation (default allowed) combined with these capabilities increases potential impact, but autonomous invocation alone is not being flagged — it's the combination with file/credential writes and process control that is notable.

What to consider before installing

This package mostly does what a local model-switcher would do, but there are important mismatches and sensitive behaviors you should check before installing: - Do not assume API keys stay only in the browser: the backend endpoints accept API keys and call secure storage/update routines. Inspect backend/secure_config.py to confirm whether API keys are encrypted at rest and how keys are written to ~/.openclaw/agents/.../auth-profiles.json. - Review any restart scripts referenced (tools/restart_gateway.bat, gateway.cmd under ~/.openclaw). Those are executed by the service (subprocess calls and taskkill) and could run arbitrary commands if modified or replaced on disk. - Confirm the server only binds to localhost in your deployment. If it binds to 0.0.0.0 or you run behind a proxy, CORS allow_origins=['*'] may expose endpoints that accept API keys to other hosts. - If you will store real production API keys, test in an isolated environment first (VM/container) to verify where keys end up and whether they are protected. - If you want to proceed, at minimum: (1) inspect secure_config.py to verify encryption, (2) restrict CORS or bind to 127.0.0.1 only, (3) review or replace restart scripts with safe versions, and (4) consider running with least privilege and backups of ~/.openclaw before first run. Because of the documentation/code disagreement about API key handling and the ability to run system commands and write to sensitive config locations, treat this skill as suspicious until you verify those details.

OpenClaw Model Switcher（模型切换工具）

一个基于 WebUI 的 OpenClaw 模型切换工具，支持快速切换 AI 模型提供商。

功能特性

• 模型通讯录：保存常用模型配置，方便重复使用
• 一键切换：点击卡片快速切换当前使用模型
• 批量导入：支持在线输入或 TXT 文件批量导入模型
• API Key 记忆：自动记住每个提供商的 API Key（本地浏览器 localStorage）
• 提供商筛选：卡片太多时可按提供商筛选
• 内置预设：阿里云、火山引擎、Kimi、DeepSeek、OpenAI、MiniMax 等

触发词

当用户提到以下内容时激活此技能：

• 「打开模型切换」「模型切换工具」「切换模型」
• 「切换到 xxx 模型」「换个模型」
• 「打开模型管理」「模型配置」
• 「切换 AI 模型」「换一个大模型」

使用方式

启动 WebUI（主要方式）

用户说「打开模型切换」后：

1. 启动后端服务（端口 9131）
2. 自动打开浏览器访问 http://127.0.0.1:9131

快速切换模型（对话式）

用户说「切换到 deepseek 模型」后，直接调用 OpenClaw 配置接口修改 openclaw.json。

技术架构

后端：Python FastAPI (端口 9131)
前端：Vue 3 + Element Plus (已构建为静态文件)
配置：~/.openclaw/openclaw.json

API 接口

接口	方法	说明
GET /api/config	GET	获取当前配置和模型列表
POST /api/save	POST	保存模型到通讯录（不重启）
POST /api/switch	POST	切换模型并重启服务
POST /api/gateway/control	POST	控制 Gateway（stop/start/restart）
POST /api/delete	POST	删除模型或提供商
GET /api/providers	GET	获取所有提供商

安全设计

• API Key 仅保存在浏览器 localStorage（本地），不上传到任何服务器
• 后端只读写 openclaw.json（不含 API Key 的部分）
• API Key 同时写入 ~/.openclaw/agents/main/agent/auth-profiles.json 供 OpenClaw 使用

依赖

• Python 3.10+
• fastapi, uvicorn, pydantic, psutil, pywin32
• Node.js（仅构建前端时需要，开发版已内置 dist）

文件结构

openclaw-model-switcher/
├── SKILL.md
├── scripts/
│   ├── start.ps1          # Windows 启动脚本
│   └── switch_model.py    # 命令行快速切换
└── assets/
    └── frontend/           # 已构建的前端静态文件
        ├── index.html
        └── assets/

快速切换命令

无需启动 WebUI，直接用 Python 脚本切换模型：

# 切换模型
python switch_model.py --provider deepseek --model deepseek-chat

# 查看当前模型
python switch_model.py --status

# 重启 Gateway
python switch_model.py --restart