caam — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited caam (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
<!-- TOC: Quick Start | Daily Operations | Rotation Doctrine | Flywheel Integration | References -->
Core Problem: You hit rate limits on your $200/mo Claude Max subscription. Browser OAuth takes 30-60 seconds. CAAM swaps accounts in ~50ms.
Don't re-learn the command surface here. caam --help (and per-subcommand --help) self-describes every command and flag; the full catalog also lives in COMMANDS.md. This skill carries the operating doctrine: how to seed the vault, when to rotate vs cooldown, and how CAAM fits the agent fleet.
Each AI CLI stores OAuth tokens in plain files (e.g. ~/.claude.json, ~/.codex/auth.json, ~/.gemini/oauth_credentials.json). CAAM backs them up to a local vault and restores them on activate. No daemons, no databases, no network calls — just cp with extra steps. Vault layout: VAULT.md.
Supported tools: Claude Code, Codex CLI, Gemini CLI (each on its own subscription).
# Install
curl -fsSL "https://raw.githubusercontent.com/Dicklesworthstone/coding_agent_account_manager/main/install.sh?$(date +%s)" | bash
# Backup current account
caam backup claude [email protected]
# Clear, login with another account, backup that too
caam clear claude
claude # /login with [email protected]
caam backup claude [email protected]
# Switch instantly forever
caam activate claude [email protected] # ~50ms, no browserA profile must be backed up once before it can ever be activated. Seed every account you own up front — mid-rate-limit is the wrong time to discover an empty vault.
The four moves that cover almost every session:
caam status # which profile is active per tool (content-hash matched)
caam activate claude --auto # rotation picks best profile (health, recency, cooldowns)
caam cooldown set claude # mark current profile rate-limited (60min default); rotation skips it
caam next claude # preview what rotation would select, without switching# Add to .bashrc/.zshrc
alias claude='caam run claude --'
alias codex='caam run codex --'
alias gemini='caam run gemini --'
# Now these auto-failover on rate limits
claude "explain this code"Link profiles to directories so work and personal accounts never cross:
cd ~/projects/work-app
caam project set claude [email protected]
caam activate claude # in this directory, auto-uses [email protected]--auto right back into the limited account.smart algorithm weighs cooldown, health, recency, and jitter. (round_robin/random exist; details in COMMANDS.md.)caam tui (blocks the terminal — keybindings self-described in-app). Agents should stick to the non-interactive commands above.| Tool | Integration |
|---|---|
| NTM | Each tmux pane uses a different account via isolated profiles — see ISOLATED-PROFILES.md |
| Agent Mail | Agents coordinate account switching across sessions |
| CASS | Search sessions by account for usage patterns |
| Topic | Reference |
|---|---|
| Complete commands | COMMANDS.md |
| Isolated profiles | ISOLATED-PROFILES.md |
| Vault structure | VAULT.md |
caam --version # verify installation
caam status # check all profiles
caam activate claude --auto && caam status # test switch~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.