Claude Warmup — Development skill for Claude Code
Manipulate Claude Code's 5-hour usage window into resetting when you actually need it.
How to install Claude Warmup
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open vdsmon/claude-warmup and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Claude Warmup does
Manipulate Claude Code's 5-hour usage window into resetting when you actually need it.
Alternatives in Development
- Root Cause Tracing — Use when errors occur deep in execution and you need to trace back to find the original trigger 102.5k ★
- Ccusage — CLI for analyzing Claude Code/Codex usage from local JSONL files 11.8k ★
- Resume Work From A Handoff Document — You are tasked with resuming work from a handoff document through an interactive process 10k ★
README
claude-warmup
Manipulate Claude Code's 5-hour usage window into resetting when you actually need it.
EDIT: You can apply the same concept and achieve the exact same goal in a "native" way by using a Claude Code Web scheduled task: https://claude.ai/code/scheduled. It works flawlessly! The "Why" section below is still very useful for visualizing why would you do this at all.
Why
Claude Code gives you a token budget that resets every 5 hours. The window starts when you send your first message, floored to the clock hour.
So if you start at 8:30 AM and burn through your budget by 11, you're locked out until 1 PM. Two dead hours in the middle of your morning.
The fix is dumb and it works: fire a throwaway message before you start working. A GitHub Actions cron sends "hi" to Haiku at 6:15 AM. The window floors to 6 AM, runs until 11. By the time you've hit the limit, it resets right away. Your next message anchors a fresh window through 4 PM.
Example schedule:
6am 7 8 9 10 11 12 1pm 2 3 4 5 6pm
| | | | | | | | | | | | |
Before: [========== window 1 =========]
work ~8:30am-11am ░░ dead ░░
[========== window 2 =========]
work ~1pm-6pm
cron trigger
│
▼
After: [========== window 1 =========]
░░ idle ░░ work ~8:30am-11am
[========== window 2 =========]
work ~11am-4pm
[== win 3 ==]
work ~4pm-6pm
As you can see, we are able to squeeze another fresh window starting at 4pm in this c
Related Skills
Claude Code Usage Quota Mod
Know your Claude limits before they hit you (Live band above the Claude Code prompt): 5 Hour and Weekly usage
Kairos
Show what is left of the five-hour usage window, and manage the gate
Claude Usage Guard
Pause Claude before its next tool call when your 5-hour or weekly plan usage runs hot with lots of window left
Nightmux
Your night crew, on Telegram. Run Claude Code, Codex or any terminal agent from a Telegram topic — one topic p
Claude Code Hud
Two Claude Code mods above the prompt box: context-window meter, 5-hour limit, prompt clocks and session cost
Agent Quota Tracker
⚡ Local CLI monitor, autonomous watchdog, and live dashboard tracking 5-hour rolling rate limits, weekly quota
Related Agents
Context Optimizer
Meta utility agent for token and context optimization. Spawn when needing to compress agent prompts, optimize
Calendar Agent
Builds a publishing calendar the creator can actually hit — cadence from the channel archetype, backwards-plan
Cmmc Reviewer
US defense-contractor (GovCon) pre-implementation reviewer. Specialises in CMMC 2.0 (Level 1 FCI / Level 2 NIS