freshlisted

# Fresh — execute a prompt at the next 5h usage reset ## Overview Detect the next 5-hour usage-window reset and fire a prompt at it, so a long run gets a **full fresh quota window**. Two modes: - **Default (same session):** one-shot `CronCreate` injects the prompt into the current session. Context is preserved. - **`--clear` (fresh session):** Windows Task Scheduler launches a brand-new headless `claude -p` session at reset. Fresh context window + fresh quota. Survives closing this session. Resumable afterwards. ## Usage ``` /fresh <prompt text | path/to/prompt.md> [--clear] [--at HH:MM] [--now] ``` If the argument is an existing file, the prompt becomes: `Execute the instructions in <absolute path>`. If it *looks* like a path but doesn't exist, stop and ask — don't schedule against a missing file or silently treat it as literal text. ## Step 1 — Find the reset time ```bash node "$HOME/.claude/skills/fresh/resolve-reset.cjs" # Windows: node "%USERPROFILE%\.claude\skills\fresh\resolve-reset.cjs" ``` Prints one JSON line: `{reset_utc, reset_local, source, utilization_pct}`. Use **`reset_local`** directly — the resolver already converted from UTC. The `source` field tells you how much to trust it: | `source` | Meaning | Confidence | |---|---|---| | `statusline-cache` | The exact value the **5h usage line** under the REPL shows (Anthropic's `/api/oauth/usage → five_hour.resets_at`, already fetched, cached 60 s). | **Authoritative.** Trust it. | | `oauth-live` | Same e