Pause an agent that hit a usage limit until its reset date, resume it, or list what is paused. Use for set a cooldown, agent is out of usage, clear a cooldown, or which agents are paused.
Install
npx skillscat add dobeu-tech-eco/dts2-marketplace/cooldown Install via the SkillsCat registry.
Directory edition: do not run bundled scripts or hooks, a package launcher, or a download piped into a shell. Do not read tokens or credential files from the machine. Carry out the step with Read, Edit, Grep, Glob, and git or gh, and write the files the step names.
Cooldown — pause an agent until its usage limit resets
Usage limits belong to the account, so one status file (~/.dts2/agent-status.json, or the path in DTS2_AGENT_STATUS) is shared by every session on the machine. The roster probe, the lead failover and the SessionStart hook all read it. A paused agent is never called, probed or picked as lead until its reset time passes; it then comes back on its own.
All commands: python3 -I "${CLAUDE_PLUGIN_ROOT}/scripts/cooldowns.py" <command>.
Steps
- set
set <agent> <date or duration> [reason]- A duration such as
2d 3hrunsset <agent> --in "2d 3h" --reason "<reason>". - A date or time such as
2026-11-21,Nov 21 9:00 AMor an ISO timestamp runsset <agent> --until "<date>" --reason "<reason>". - A date that cannot be read exits 2: ask for another form once.
- A duration such as
- clear
clear <agent>removes the pause now (the limit was lifted early, or the date was wrong). - list
listshows the agents paused now with their reset time and reason;list --allalso shows entries that have ended. - Confirm in one line: which agent is paused, until when (local time and UTC), and that it is skipped everywhere until then.
First agent to hit a limit
When a dispatch or a call fails with a usage, quota or rate-limit message:
- Pipe the output to
detect --agent <agent> --exit-code <n> --record. - If the result says
"limited": false, this is not a usage limit; handle it as an ordinary failure. - If it says
needs_date: true, ask the user ONCE for the reset date or duration, then runset <agent> --until "<date>" --source user. A provisional pause of about five hours stays in place until they answer. - Tell the user which agent is paused and until when, then continue the work with the remaining agents.
- Never re-probe or re-call a cooling agent.
check <agent>exits 3 while it is paused; do not try to "see if it is back".
Notes
- A limit that resets in under 15 minutes is not recorded; wait and retry instead.
- A later, shorter detection never shortens a pause that is already active; only
set(a person's word) does. - The SessionStart hook prints which agents are paused, and which came back, at the start of each session.