T06 · System Persistence
- Location
scripts/ensure-shared-memory-crons.js:57- Finding
Persistent Scheduled Agent Jobs with Shell Execution Access
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill mostly matches its memory-governance purpose, but it creates persistent scheduled agent jobs with read/exec access and gives risky plaintext secret-storage guidance.
Review this skill carefully before installing. Only use it in a trusted workspace where persistent OpenClaw cron jobs with read and command-execution access are acceptable, inspect or disable the scheduled jobs after setup, avoid storing real credentials in memory/private-secrets.md, and change the hardcoded workspace path and timezone before use outside that exact environment.
scripts/ensure-shared-memory-crons.js:57Persistent Scheduled Agent Jobs with Shell Execution Access
scripts/find-promotion-candidates.js:7Stored Prompt Injection Through Untrusted Learning Content and Scheduled Report Review
references/private-secrets-template.md:3Plaintext Storage of API Keys and Bot Tokens in Workspace Memory
The declared description presents a broad shared-memory governance system for multi-agent workspaces, including memory tiers, capture, promotion review, lifecycle management, reporting, and documentation. The supplied code chunk does something narrower and materially different: it reads .md files from the .learnings directory, searches for certain keywords, and emits optimization suggestions tied to other skills. While it does touch learnings content in the workspace, that is only a small adjacent aspect of the declared purpose. The primary behavior is recommendation generation, not governance or memory management, so the description does not accurately represent this code chunk.
The supplied code performs a narrow file-migration task: it reads Markdown files from a notes directory, copies them into a memory directory, and outputs a migration summary. This does relate loosely to memory management, but it does not implement the extensive governance capabilities described. The declared description suggests a comprehensive shared-memory governance system, while the actual code is only a migration utility. That is a materially different primary purpose, so this should be flagged as a mismatch.
Referenced artifact was not completely inspected
- `scripts/ensure-shared-memory-crons.js`
Referenced artifact was not completely inspected
- `scripts/ensure-shared-memory-crons.js`
Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.
4. review repeated lessons
5. promote stable repeated lessons into `MEMORY.md` or skill rules
This keeps the workspace learning system adaptive without requiring a runtime self-modifying agent.
Without declared permissions the skill's intent is opaque and cannot be validated.
The skill instructs the agent to immediately create or update recurring cron jobs and run a full maintenance pass, which introduces persistent automation changes to the workspace without requiring explicit user confirmation or presenting a warning. In an agent context, this can create lasting scheduled execution with exec/read capability, surprising the operator and expanding the blast radius beyond the current session.
The manifest describes memory governance, reporting, lifecycle management, and collaboration features, but this file implements process spawning through child_process.execFileSync to run multiple subordinate scripts. While orchestration may be part of setup, direct subprocess execution is a broader operational capability than the manifest explicitly conveys.
The script forces all cron jobs to use Asia/Shanghai via a fixed TZ value. This is a locale policy issue because it imposes a specific regional setting on all users without offering a choice or documenting why that locale is required.
The script forces TZ="Asia/Shanghai" for all cron jobs it creates or edits. This is a locale policy concern because the file does not offer user choice or explain why that region-specific timezone is required, so executions may occur at unexpected local times for other users or environments.
This shell script writes to temporary JSON state and, more importantly, creates or updates cron jobs via openclaw cron add/edit, which changes persistent scheduler configuration. While there is some machine-readable output at the end, there is no user-facing warning, confirmation prompt, or explanatory comment/docstring disclosing that the script will alter scheduled jobs and job storage.
This markdown file instructs the user to enable health checks and a weekly review cron, which implies creating or modifying a scheduled task on the user's system. The guide provides no warning about the persistence or system-impacting nature of that operation.
This code creates a directory and writes a markdown file to a fixed workspace path, but there is no confirmation prompt, inline comment, or docstring disclosing that it will modify the filesystem. Aside from printing the output path after the write, the script does not warn the user beforehand that it creates persistent files under the workspace.