T06 · System Persistence
- Location
SKILL.md:92- Finding
Automatic Creation of Persistent Scheduled Jobs with Command Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill does model-registry maintenance, but it also creates persistent jobs, uses API keys against unvalidated endpoints, and can overwrite live OpenClaw configuration without enough guardrails.
Review before installing. Use this only in a controlled OpenClaw environment with backed-up configuration, trusted provider base URLs, scoped and revocable API keys, and explicit approval for any cron jobs, `.learnings/` writes, config changes, or gateway restarts.
SKILL.md:92Automatic Creation of Persistent Scheduled Jobs with Command Execution
SKILL.md:64Unprompted Writes to Persistent Agent Learning State
scripts/sync-models.js:44Synchronization Script Sends API Credentials to Unvalidated Provider Endpoints
scripts/validate-model-sync.js:26Validation Script Sends API Credentials to Unvalidated Provider Endpoints
scripts/sync-models.js:118Partial or Failed Synchronization Can Destructively Erase Model Catalog Entries
The documented purpose says the skill performs safe registry synchronization, but the behavior described includes active probing of provider endpoints with API-backed access and scheduled operational validation. This mismatch can mislead operators into approving or invoking a skill under narrower assumptions than its real behavior, causing unreviewed external calls and persistent automation.
Referenced artifact was not completely inspected
- `SKILL.md`: only workflow + decision rules
The skill instructs network access and operational actions against provider endpoints, but it does not declare an explicit tool scope such as allowed tools or permissions. That creates an authorization gap where an agent may run with broader-than-necessary capabilities, increasing the chance of unintended network access or access to sensitive environment-backed credentials.
The invocation guidance is broad enough to trigger the skill in general model-management situations, even when persistent changes, probing, or scheduling may be inappropriate. Over-broad activation criteria increase the chance of the agent performing network calls, config edits, or cron setup in contexts where the user only wanted inspection or advice.
The skill directs automatic persistence of run-derived information into .learnings/ as a default closing step, without requiring explicit user consent or a sensitivity check. This can store user corrections, operational failures, or workspace-specific details persistently, creating data leakage, retention, and prompt-injection persistence risks across future runs.
Skill injects content designed to persist in agent memory or context across interactions. Persistent injection can alter agent behavior long after the initial interaction.
- per-provider sync + global catalog merge
### Avoid hardcoding
- exact vendor model ids as permanent rules
- one provider’s naming quirks as universal truth
- one-off emergency fixes in the main sync algorithm
- model routing policy into registry sync
The skill recommends creating or updating recurring cron jobs, which is a persistent system or workspace change, but it does not require an explicit warning and confirmation before doing so. Persistence plus scheduled execution can repeatedly trigger network access, script execution, and configuration changes long after the original interaction, making mistakes or abuse much more damaging.
The scheduled job guidance allows broad command execution via toolsAllow including exec for a task whose purpose is limited to model sync and validation. Granting exec to recurring jobs expands the blast radius of any prompt mistake, script compromise, or downstream misuse into arbitrary command execution on every scheduled run.
The script overwrites the primary OpenClaw configuration file directly when not run with --dry-run, with no confirmation prompt, backup, or safer staged write. Because the file controls provider endpoints, API-backed model registration, and downstream agent defaults, an operator can unintentionally destroy or replace working configuration state, especially if remote provider data is incomplete or maliciously manipulated.
When --restart is supplied, the script immediately runs 'openclaw gateway restart' after changing configuration, without a confirmation step or guardrail. In this skill's context, the script is modifying live model registry state based on remote provider responses, so an unsafe or accidental run can trigger service disruption or apply bad config directly to production-facing components.
This code performs HTTP requests to external provider endpoints using an Authorization bearer token and sends model IDs in request bodies, but the file contains no docstring, comment, or user-facing disclosure explaining that network calls and credential-backed probes will occur. For a code file, these are safety-relevant operations involving external transmission of system and configuration data.
The skill explicitly states it should stay focused on model registry sync and should not bundle broader operational policy, yet later sections prescribe workspace scheduling, job structure, delivery mode, and failure alert behavior. These instructions expand the skill into ongoing operational orchestration, which conflicts with the earlier documented boundary that the skill remain focused on registry sync and validation.
The markdown specifies 'Recommended default schedules (Asia/Shanghai)', which hard-codes a locale/timezone preference. This is a natural-language locale policy choice presented as the default without offering the user a choice or explaining why that region is required.
The script creates a reports directory and writes JSON and Markdown report files, but there is no comment, docstring, or other in-file disclosure that local filesystem state will be modified. This meets the code-file criterion for file writes lacking any form of user warning or explanation.