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:

1. Read the list of registered cron skills from OpenClaw config
2. For each skill, check its session mode (main vs isolated)
3. Estimate cost impact: crons in main mode × frequency × estimated context size
4. Flag violations and surface recommendations

Hygiene rules