Model Guard
PassAudited by ClawScan on May 10, 2026.
Overview
Model Guard appears to do what it claims—checking OpenClaw model quotas and switching the default model—but only install or schedule it if you want that automatic model-control behavior.
Before installing, confirm that you want a tool to automatically change your OpenClaw default model. Review guard.js, especially the hard-coded candidate models, the 20% threshold, the fallback model, and the assumption that some Gemini Anti-Gravity models have 100% quota when not listed. If you run it through cron or heartbeat, make sure you know how to disable that schedule.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The skill can automatically change which model your agent uses, which may affect behavior, quality, latency, or cost.
The skill shells out to the OpenClaw CLI and can change the configured default model. The commands are purpose-aligned and bounded by hard-coded model choices, but this is still a meaningful control action.
return execSync(cmd, { encoding: 'utf8', stdio: ['ignore', 'pipe', 'ignore'] }).trim(); ... run(`openclaw models set ${bestModel}`);Review the hard-coded model list, THRESHOLD, and FALLBACK_MODEL before use, and only run or schedule it if automatic model switching is desired.
It acts with whatever OpenClaw account/configuration permissions are available in the environment where it runs.
The skill uses the user's existing OpenClaw CLI context to read model status and modify the default model. The artifacts do not show credential logging, token handling, or unrelated account access.
const statusText = run('openclaw models status'); ... run(`openclaw models set ${FALLBACK_MODEL}`);Run it only in an OpenClaw environment where changing the default model is acceptable, and reset the model manually if you no longer want its choice.
If scheduled, it may keep changing the default model until the cron or heartbeat configuration is removed.
The skill is explicitly intended for recurring execution if the user configures a scheduler. It does not install that persistence itself, but scheduled use would continue changing models over time.
- **Auto trigger**: Designed to be run via `cron` or `heartbeat`.
If you schedule it, document where the schedule is configured and how to disable it.
You have less external context for who maintains the skill or where to verify updates.
The skill's provenance is not documented in the provided metadata. The included code is small and reviewable, so this is a provenance note rather than evidence of malicious behavior.
Source: unknown; Homepage: none
Review the included source before installing and prefer trusted sources or pinned versions for ongoing use.