OpenClaw Model Router Skill

Deterministic model routing for OpenClaw with prefix routing (@codex/@mini), timezone-aware schedule switching, verify-after-switch, rollback, lock protectio...

Security Scan

The code, configs, and runtime instructions match the stated purpose (deterministic model routing, schedule-based switching, verification/rollback, logging and locking); nothing requested or implemented is disproportionate to that purpose.

Purpose & Capability

Name/description map to code and configs: prefix routing, schedule file, switch/verify/rollback flow, lock file and JSONL logging. The files and CLI implement exactly these features; required binaries and envs are configurable and default to safe values in the provided router.config.json.

Instruction Scope

SKILL.md commands and runbook instruct running the included CLI (node src/cli.js) and manipulating local config/schedule/log files. Runtime instructions do not request unrelated system data or external endpoints. They do call a local session controller binary (default 'openclaw') to query/set the active model, which is consistent with a model router.

Install Mechanism

No install spec (instruction-only distribution) — code is included in the package and intended to be run with node. No downloads or external installers are invoked. This is low risk given the code is present in the skill bundle and not fetched from arbitrary URLs.

Credentials

By default router.config.json.auth.requiredEnv is empty so no credentials are required. The code supports an auth.requiredEnv list which, if populated, will cause the CLI to check for those environment variables before switching. That's reasonable for an auth gate, but if you populate requiredEnv you should ensure only the needed secrets are present. Child processes inherit process.env when execFile is used, so any env secrets present will be visible to the invoked session-controller binary.

Persistence & Privilege

The skill does not request always:true and does not attempt to modify other skills or global agent configuration. It writes local lock and log files and reads local config/schedule files — behavior expected for a scheduler/router.

Assessment

This skill appears coherent and implements a local model router. Before installing or running in production: 1) Review router.config.json and router.schedule.json — confirm sessionController.binary points to a trusted binary (default 'openclaw') and that set/status args are correct. 2) If you populate auth.requiredEnv, only include the minimum secrets required and verify where those env vars are set. Child processes inherit process.env, so environment secrets will be exposed to the invoked binary. 3) The CLI writes lock and JSONL log files in the working directory by default; ensure file paths and rotation meet your operational policies. 4) Do not point sessionController.binary to an arbitrary or untrusted executable; that would let the skill run arbitrary commands. If you want extra assurance, run the tool in an isolated/test environment and audit the invoked binary's behavior before giving it access to production credentials or systems.

Deterministic model routing with a closed-loop production switch pipeline.

Why use this skill

• Explicit user intent routing (@codex, @mini)
• Time-window model policy (router.schedule.json)
• Safe switch flow with verification and rollback
• Concurrency lock to prevent race conditions
• Structured audit logs for operations and incident review

Core capabilities

1. Prefix routing

• @codex → openai-codex/gpt-5.3-codex
• @mini → minimax/MiniMax-M2.5
• Aliases: @c, @m

2. Scheduler routing

• Rule-based windows by day/time/priority
• Timezone-aware resolution (router.schedule.json.timezone)
• Supports overnight windows (e.g. 18:00 → 09:00)

3. Production switch loop

• schedule apply / schedule end
• Auth gate (auth.requiredEnv[])
• Switch + readback verify
• Failure classification (auth_expired, rate_limit, provider_drift, unknown)
• Optional rollback (safety.rollbackOnFailure)
• Lock file (safety.lockPath) to avoid concurrent switching
• Audit logs (router.log.jsonl + rotation)

Quick commands

# Validate config
node src/cli.js validate

# Route inspection
node src/cli.js route "@codex implement this" --json

# Scheduler
node src/cli.js schedule validate
node src/cli.js schedule resolve --at "2026-03-02T10:00:00+01:00" --json
node src/cli.js schedule apply --json
node src/cli.js schedule end --id workday_codex --json

Key config files

• router.config.json (prefix map, retry, auth, safety, logging, controller)
• router.schedule.json (timezone + rules)

Reliability checklist

• Deterministic mapping
• Idempotent switching behavior
• Execute only after switch verification
• Observable success/failure events
• Recoverability on failure paths

Tests

node --test