← ClaudeAtlas

usage-guardlisted

Arm proactive 5-hour usage protection for long Claude Code sessions (batch, subagents, high window % at start). Daemon reads account-level 5-hour window usage (not per-session). User types /usage-guard at session start. Re-arm every sitting. If user mentions usage-guard by name, read this file and run arm.sh.
shirley-xue-2025/usage-guard · ★ 15 · AI & Automation · score 76
Install: claude install-skill shirley-xue-2025/usage-guard
# usage-guard Proactive usage guard for long Claude Code sessions (Desktop Code tab or CLI). **Invoke once at session start** before heavy batch, subagent, or overnight work — especially when the account window is already partly used. ### Why account-level monitoring matters Each Claude session only sees its own usage. The **shared 5-hour window** is account-level — you can start at 58% in one session while another tab or earlier work already pushed the window to 94%. The daemon polls the OAuth usage API (same as Desktop Settings) so the guard sees the real window, not just this chat's view. ### Re-arm every sitting **Arms do not survive** Desktop quit, crash, or daemon exit. At the start of **every** new sitting, run `/usage-guard` (or `/usage-guard resume` if continuing a paused task). If `arm.sh` prints `"warning"`, the previous guard was stale — proceed with the new arm. ## If the user mentions usage-guard without `/usage-guard` When the user says "use usage-guard", "pay attention to usage limits", or names this skill but does not run the slash command: 1. **Follow this file** (you are reading it — treat that as the contract). 2. Run `arm.sh` via bash before heavy work (same as ARM MODE below). 3. Tell the user: `/usage-guard` is the normal entry point; with `disable-model-invocation` it may not show in the slash picker — **typing `/usage-guard` still works**. Do **not** auto-arm on your own initiative without the user asking for usage protection. ## When the us