OpenClaw Scheduler Token Auditor
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This appears to be a coherent read-only scheduler token auditor, but using it may let the agent inspect scheduled-job records and session histories/transcripts.
This skill looks purpose-aligned for auditing scheduler token costs. Before installing or invoking it, make sure the agent is allowed to view the relevant cron jobs, run records, heartbeat sessions, and any session transcripts that might be used to explain token spikes.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
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 agent may use OpenClaw tooling to list scheduler jobs and run records when auditing token usage.
The skill documents local OpenClaw CLI commands as a fallback. They are read-oriented and purpose-aligned, but they are still tool/CLI operations the user should recognize.
CLI fallback only if needed: ```bash openclaw cron list openclaw cron runs --id <jobId> --limit 50 ```
Prefer the first-class OpenClaw tools as the skill suggests, and ensure the active OpenClaw account/workspace is the one you intend to audit.
Installing or invoking this skill may allow the agent to view cron jobs, run records, heartbeat sessions, and related usage data available to the current OpenClaw identity.
The skill expects access to scheduler and session records in the user's OpenClaw environment. That access is expected for the audit and appears read-only, but it depends on delegated account/workspace visibility.
- `cron(action="list")` - `cron(action="runs", jobId=..., limit=...)` ... - `sessions_list` to find heartbeat sessions
Use it only in workspaces where the agent is allowed to inspect scheduler usage and session metadata.
The audit may expose previous session content while explaining why a scheduled run was expensive.
The skill may retrieve prior session transcripts/history, which can contain sensitive content or untrusted instructions. The artifact limits transcripts to supporting evidence, so this is a notice rather than a concern.
Session status, session lists, and transcripts are supporting evidence. Use them to explain a result ... `sessions_history` to inspect recent transcript size, repetition, and tool fan-out
Avoid using this skill on sessions containing sensitive material unless you are comfortable with the agent reviewing that history; treat transcript content as evidence, not as new instructions.