Agent skill

Account Rotator for Usage Limits

Switches to the next connected Claude or Codex account that has proven capacity when a session or weekly usage limit is hit, using the headroom CLI.

MITAuto-check passedProductivity & Automation

Install Account Rotator for Usage Limits

skills CLI

$ npx skills add domanski-ai/headroom --skill rotator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install domanski-ai/headroom rotator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/domanski-ai/headroom.git skills-src && mkdir -p .claude/skills && cp -r skills-src/integrations/claude-code/skills/rotator .claude/skills/rotator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "rotator" agent skill from https://github.com/domanski-ai/headroom/tree/master/integrations/claude-code/skills/rotator into .claude/skills/rotator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rotator", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/domanski-ai/headroom/tree/master/integrations/claude-code/skills/rotator

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add domanski-ai/headroom --skill rotator -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install domanski-ai/headroom rotator --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/domanski-ai/headroom.git skills-src && mkdir -p .agents/skills && cp -r skills-src/integrations/claude-code/skills/rotator .agents/skills/rotator && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "rotator" agent skill from https://github.com/domanski-ai/headroom/tree/master/integrations/claude-code/skills/rotator into .agents/skills/rotator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rotator", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add domanski-ai/headroom --skill rotator -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install domanski-ai/headroom rotator --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/domanski-ai/headroom.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/integrations/claude-code/skills/rotator .cursor/skills/rotator && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "rotator" agent skill from https://github.com/domanski-ai/headroom/tree/master/integrations/claude-code/skills/rotator into .cursor/skills/rotator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rotator", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/domanski-ai/headroom.git --path integrations/claude-code/skills/rotator

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add domanski-ai/headroom --skill rotator -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install domanski-ai/headroom rotator --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/domanski-ai/headroom.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/integrations/claude-code/skills/rotator .gemini/skills/rotator && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "rotator" agent skill from https://github.com/domanski-ai/headroom/tree/master/integrations/claude-code/skills/rotator into .gemini/skills/rotator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rotator", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install domanski-ai/headroom rotator

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add domanski-ai/headroom --skill rotator -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/domanski-ai/headroom.git skills-src && mkdir -p .github/skills && cp -r skills-src/integrations/claude-code/skills/rotator .github/skills/rotator && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "rotator" agent skill from https://github.com/domanski-ai/headroom/tree/master/integrations/claude-code/skills/rotator into .github/skills/rotator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rotator", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add domanski-ai/headroom --skill rotator -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install domanski-ai/headroom rotator --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/domanski-ai/headroom.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/integrations/claude-code/skills/rotator .opencode/skills/rotator && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "rotator" agent skill from https://github.com/domanski-ai/headroom/tree/master/integrations/claude-code/skills/rotator into .opencode/skills/rotator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rotator", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: rotator
GitHub stars: 107
Token cost: ~483 tokens
SKILL.md length: 221 words
Files: 1
Skills in repo: 1
Repo updated: Aug 25, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Switches to the next connected Claude or Codex account that has proven capacity when a session or weekly usage limit is hit, using the headroom CLI.

Works in 4 steps: Run headroom rotate (default model… → Relay the one-line result to the user… → If it exits 2, every account is limited.… → …
Hitting a session or weekly usage limit on one connected account
SKILL.md covers When to fire, What to do and Guardrails
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

When a command or session fails with a session, weekly or usage-limit error, or you ask which account has capacity, the agent runs headroom rotate for the chosen model family (claude by default). The tool cools the exhausted account down until its window resets, picks the next login with proven headroom in your configured preference order and prints the export line for it. The agent relays the one-line result as it is.

If every account is limited, the command exits with code 2 and the agent reports the earliest reset time instead of failing silently or switching to a weaker model. A status view is available through headroom status. Account changes go through headroom connect and setup, never by editing the config file by hand. The new account applies to new sessions that inherit CLAUDE_CONFIG_DIR or CODEX_HOME, so the current session needs a restart to move.

When your agent uses it

Hitting a session or weekly usage limit on one connected account
Checking which of your accounts still has capacity
Seeing when an exhausted account becomes usable again

Example prompts

“I hit my weekly limit. Rotate to the next account.”
“Run /rotator codex, since the Codex session just hit its limit.”
“Which of my connected accounts has headroom left right now?”

Requirements

The headroom CLI with connected accounts configured

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Run headroom rotate (default model family: claude).
Relay the one-line result to the user exactly
If it exits 2, every account is limited. Report the earliest reset time it
For a status view first, run headroom status and show the table.

What it can do on your machine

Read from SKILL.md and the folder at commit 4cdc772. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Account Rotator for Usage Limits loads about 483 tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 221 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~99
When it runs · the whole SKILL.md, loaded when a task matches: ~483

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from domanski-ai/headroom at commit 4cdc772, republished under its MIT licence (© domanski-ai). 221 words, ~483 tokens.

Download SKILL.mdSave it as .claude/skills/rotator/SKILL.md (or your agent's skills folder).

name: rotator
description: Rotate to the next connected account with proven headroom when a usage limit hits. Triggers: /rotator, rotate the account, hit my session limit, hit the weekly limit, out of usage, switch account, no headroom left, which account has capacity. Uses the headroom CLI to pick the next eligible login in your configured preference order and cool the exhausted one down until its window resets.

rotator

Rotate BETWEEN connected logins for the same provider when one hits a usage limit. Powered by the headroom CLI (https://github.com/domanski-ai/headroom).

When to fire

The user types /rotator (optionally /rotator <model>, default claude).
A command or session fails with a session/weekly/usage-limit or 429 error.
The user asks which account has capacity, or says they are out of usage.

What to do

Run headroom rotate <model> (default model family: claude). It cools the current account down until its window resets, picks the next login with PROVEN headroom, and prints the export line for the new account.
Relay the one-line result to the user exactly: rotated <old> -> <new> (<family>); <old> cools until <reset>.
If it exits 2, every account is limited. Report the earliest reset time it printed — never silently fail, never downgrade the model.
For a status view first, run headroom status <model> and show the table.

Guardrails

Never edit ~/.headroom/config.json by hand from this skill; account changes go through headroom connect / headroom setup.
Cooldowns are fail-closed: if headroom says nobody has proven capacity, believe it. Do not retry the limited account "just in case".
The new account takes effect for NEW sessions/processes that inherit CLAUDE_CONFIG_DIR (or CODEX_HOME). The current interactive session keeps its own login; tell the user to restart the session if they want it moved.

Files

Just SKILL.md in integrations/claude-code/skills/rotator of domanski-ai/headroom.

Open the folder on GitHubat commit 4cdc772

Compare with similar skills

Account Rotator for Usage Limits next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Account Rotator for Usage Limits compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Account Rotator for Usage Limits this skilldomanski-ai/headroom	107	—	~483	Automated safety check: Pass	MIT	1 mo ago
Agent Browser CLIvercel-labs/agent-browser	44k	24 repos	~864	Automated safety check: Pass	Apache-2.0	2 days ago
Dev Browser AutomationMemTensor/MemOS	12k	3 repos	~1.7k	Automated safety check: Pass	Apache-2.0	yesterday
Electron App Automationvercel-labs/agent-browser	44k	5 repos	~1.7k	Automated safety check: Pass	Apache-2.0	2 days ago
Next Dev Loopvercel/next.js	143k	9 repos	~2.3k	Automated safety check: Pass	MIT	today
Skyvern Browser AutomationSkyvern-AI/skyvern	23k	1 repos	~2.9k	Automated safety check: Pass	AGPL-3.0	today

Similar skills

Agent Browser CLI
vercel-labs/agent-browser
Official
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking…
44k GitHub starsUsed in 24 repos~864 tokens
Productivity & AutomationAuto-check passed
Dev Browser Automation
MemTensor/MemOS
Automates a real browser through short TypeScript scripts that keep page state between runs, for navigating, filling forms, taking screenshots and extracting data.
12k GitHub starsUsed in 3 repos~1.7k tokens
Productivity & AutomationAuto-check passed
Electron App Automation
vercel-labs/agent-browser
Official
Automates Electron desktop apps such as VS Code, Slack or Discord by connecting agent-browser to their Chrome DevTools Protocol port.
44k GitHub starsUsed in 5 repos~1.7k tokens
Productivity & AutomationAuto-check passed
Next Dev Loop
vercel/next.js
Official
Verify Next.js runtime behavior after editing app code. An agent skill from vercel/next.js.
143k GitHub starsUsed in 9 repos~2.3k tokens
Productivity & AutomationAuto-check passed
Skyvern Browser Automation
Skyvern-AI/skyvern
Picks the right Skyvern CLI command for a web task, from quick yes/no checks to reusable multi-page workflows, instead of falling back to plain page fetching.
23k GitHub starsUsed in 1 repo~2.9k tokens
Productivity & AutomationAuto-check passed
Dependency Watch
telegramdesktop/tdesktop
Audit Telegram Desktop dependencies on freshly fetched origin/dev for releases and security fixes, including upstream lag and backport candidates in patched forks.
33k GitHub stars~2.2k tokensUpdated today
Productivity & AutomationAuto-check passed

Questions about Account Rotator for Usage Limits

What does Account Rotator for Usage Limits do?

Switches to the next connected Claude or Codex account that has proven capacity when a session or weekly usage limit is hit, using the headroom CLI. When a command or session fails with a session, weekly or usage-limit error, or you ask which account has capacity, the agent runs headroom rotate for the chosen model family (claude by default). The tool cools the exhausted account down until its window resets, picks the next login with proven headroom in your configured preference order and prints the export line for it.

When should I use Account Rotator for Usage Limits?

Account Rotator for Usage Limits fits situations like: hitting a session or weekly usage limit on one connected account; checking which of your accounts still has capacity; seeing when an exhausted account becomes usable again.

How do I install Account Rotator for Usage Limits in Claude Code?

Run `npx skills add domanski-ai/headroom --skill rotator -a claude-code`. Or copy the skill folder (integrations/claude-code/skills/rotator in domanski-ai/headroom) into .claude/skills/rotator in your project. Claude Code loads it when a task matches its description.

How do I install Account Rotator for Usage Limits in Codex?

Run `npx skills add domanski-ai/headroom --skill rotator -a codex`. Or copy the skill folder (integrations/claude-code/skills/rotator in domanski-ai/headroom) into .agents/skills/rotator in your project. Codex loads it when a task matches its description.

Can I use Account Rotator for Usage Limits in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add domanski-ai/headroom --skill rotator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rotator, .gemini/skills/rotator, .github/skills/rotator and .opencode/skills/rotator in your project.

What does Account Rotator for Usage Limits need to run?

SKILL.md names no scripts, command-line tools or credentials: Account Rotator for Usage Limits is instructions for the agent only. Our summary lists: The headroom CLI with connected accounts configured.

Does Account Rotator for Usage Limits access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Account Rotator for Usage Limits safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Account Rotator for Usage Limits use?

Account Rotator for Usage Limits is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Account Rotator for Usage Limits use?

About 483 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Account Rotator for Usage Limits?

Skills that share tags, products or a category with Account Rotator for Usage Limits: Agent Browser CLI (vercel-labs/agent-browser, 44k stars), Dev Browser Automation (MemTensor/MemOS, 12k stars), Electron App Automation (vercel-labs/agent-browser, 44k stars) and Next Dev Loop (vercel/next.js, 143k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Account Rotator for Usage Limits?

domanski-ai (a GitHub user) maintains it in domanski-ai/headroom, which has 107 GitHub stars. The repository was last updated on August 25, 2026.

Source: domanski-ai/headroom on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Account Rotator for Usage Limits

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

rotator

When to fire

What to do

Guardrails

Files

Compare with similar skills

Similar skills

Agent Browser CLI

Dev Browser Automation

Electron App Automation

Next Dev Loop

Skyvern Browser Automation

Dependency Watch

Related

Questions about Account Rotator for Usage Limits