cron-hygiene
cron-hygiene
Cron jobs running in main session mode inherit the full conversation history — re-sending thousands of tokens of context on every invocation. A cron running every 5 minutes in main session mode can turn a $10/month setup into $80+ (issue #20092). This skill audits all configured cron skills weekly and enforces hygiene standards.
Difference from context-budget-guard
context-budget-guard monitors live session token usage in real-time. cron-hygiene is about the structural problem: cron jobs that are architecturally wasteful because they're configured in the wrong session mode.
Cron Wakeup Behaviour
Runs every Monday at 09:00 (cron: "0 9 * * 1"). On each wakeup:
- Read the list of registered cron skills from OpenClaw config
- For each skill, check its session mode (
mainvsisolated) - Estimate cost impact: crons in
mainmode × frequency × estimated context size - Flag violations and surface recommendations
Hygiene rules
More from archieindian/openclaw-superpowers
context-window-management
Prevents context overflow on long-running OpenClaw sessions. Use when approaching context limits.
28heartbeat-governor
Enforces per-skill execution budgets for scheduled cron skills — pauses runaway skills that exceed their token or wall-clock budget before they drain your monthly API allowance.
27using-superpowers
Bootstrap skill — teaches the agent how to find and invoke skills. Use when starting any new task or session.
23long-running-task-management
Breaks multi-hour tasks into checkpointed stages with resume capability. Use when a task is expected to take more than 30 minutes or multiple sessions.
22fact-check-before-trust
Triggers a secondary verification pass for any agent output containing factual claims, numbers, dates, or named entities before the output is acted on
21persistent-memory-hygiene
Keeps OpenClaw's memory store clean, structured, and useful. Use at session end and during periodic maintenance.
20