Ops Accounts logo

Ops Accounts

Organization
Lifecycle-Innovations-Limited
ops-accounts

OPS on-demand: This skill should be used when the user asks to "rotate accounts", "switch…

Overview

PublisherLifecycle-Innovations-Limited
Repositoryclaude-ops
Skill nameops-accounts
Stars
543
Forks
64
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Lifecycle-Innovations-Limited on GitHub. Read the source before you install it.

Installation

Install the Ops Accounts AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-accounts
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git /tmp/claude-ops
mkdir -p .claude/skills
cp -r /tmp/claude-ops/claude-ops/skills/ops-accounts .claude/skills/ops-accounts
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ops Accounts in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ops Accounts on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ops Accounts is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

OPS ► ACCOUNTS

Load ops-rules before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If AskUserQuestion / Workflow are missing, follow Rule 10 in ops-rules (Hermes: numbered options / two-turn Telegram card; delegate_task).

Canonical multi-provider seat manager. Same layers Anthropic has for Claude — for every provider:

LayerVerbs
Status / liststatus, list
Setup / OAuth capturesetup
Switch active seatswitch, rotate-now (Claude)
Refresh tokensrefresh
Unattended reauthreauth
Utilization / quotautil
Pooled seats across accountsCLIProxyAPI (see /ops:ops-fleet)

Aliases (compat): /ops:rotate → this skill (Claude-focused shortcuts).
/ops:rotate-setup → setup (wizard). /ops:account → same as this skill.

Providers

ProviderEngineReauthUtil
Claudescripts/account-rotation/rotate.mjs + staged enrollmentsigned stage/activate only5h/7d
Grokslots + grok-cli-auth-proxydevice-code + Google (dcli); residential egress cascadeweekly / 429
OpenAI / Codexcodex-rotate when presentOAuth bridgeusage best-effort
Factoryadapter TBD / quota-feed seedsnativequota-feed patterns
Cursoradapter TBDbrowser/device OAuthplan limits if available

CLIProxyAPI is the only supported multi-account path. It holds one OAuth seat file per account and answers locally; rotate.mjs writes those seat files as part of a rotation. The earlier relay backend (claude-relay-service) has been removed — it required a static bearer token in settings.json for every session. For Grok, multi-seat round-robin lives on grok-cli-auth-proxy.

Router (bin/ops-accounts)

Always prefer:

bash
PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-$(ls -d "$HOME/.claude/plugins/cache/ops-marketplace/ops"/*/ 2>/dev/null | sort -V | tail -1)}"
"$PLUGIN_ROOT/bin/ops-accounts" <cmd> …
CommandAction
status / listAll configured providers (no secrets)
util [claude|grok|all]Quota / utilization best-effort
switch claude / rotate-nowClaude keychain rotate (force-rotate / rotate.mjs)
switch grokNext SuperGrok seat (grok-rotate switch)
refresh [all|claude|grok]Keepalive / RT refresh
reauth claude <email>Fails closed with staged-enrollment handoff
reauth grok <email>Device reauth with residential cascade env
setup / setup claudeClaude direct auth is disabled; staged enrollment required
setup grokAdd/reauth SuperGrok seat
seatsLocal multi-provider seat-state
gatewayLocal OpenAI-compat gateway: status/start/path/self-test/config

Claude setup / OAuth

When $ARGUMENTS is setup, setup claude, or this skill is invoked via ops-rotate-setup alias: follow the full wizard in skills/ops-rotate-setup/SKILL.md. That file remains the detailed Claude setup procedure; this skill is the entrypoint.

Claude day-2 ops (status/rotate-now/list/reauth) also match skills/ops-rotate/SKILL.md — treat that as Claude detail appendix.

Local seat-state

bash
"$PLUGIN_ROOT/bin/ops-accounts" seats status
"$PLUGIN_ROOT/bin/ops-accounts" seats import-claude-config
node "$PLUGIN_ROOT/scripts/account-rotation/seat-state.mjs" toggle claude <email> false

File: $CLAUDE_PLUGIN_DATA_DIR/account-rotation/seat-state.json (or OPS_ACCOUNTS_STATE_PATH).

Grok notes

  1. CLI models often use base_url → host OAuth proxy → SuperGrok seats.
  2. grok-rotate / auth.json is the SuperGrok seat set; keep auth-slots in sync after reauth.
  3. Reauth egress: EFG SOCKS (GROK_REAUTH_SOCKS) → Bright Data tiers via
    scripts/account-rotation/grok-reauth-egress.sh (residential cascade).
  4. Proxy RR status: curl -sS http://127.0.0.1:31845/accounts (no tokens).

Rules

  1. Never print tokens, cookies, OTP codes, or vault dumps.
  2. Never write real emails into committed files.
  3. Prefer bin/ops-accounts over ad-hoc host paths.
  4. A missing CLIProxyAPI is not a failure — single-seat rotation works without it.
  5. Dead RT → reauth, never a relay install.
  6. Background long OAuth (Rule 4).

Phase map

0 contract + this skill · 1 Claude parity · 2 CLIProxyAPI pool · 3 Grok complete ·
4 Codex+Factory · 5 Cursor · 6 companions · 7 host cutover · 8 local gateway

Frequently asked questions

What does the Ops Accounts AI skill do?

OPS on-demand: This skill should be used when the user asks to "rotate accounts", "switch…

Why use Ops Accounts on TypingMind?

Because you install it once and use it with any model. Ops Accounts is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ops Accounts in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-accounts. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Ops Accounts?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ops Accounts?

As many as you like. As long as a model supports skills, you can use Ops Accounts with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ops Accounts AI skill free?

Yes. It is published on GitHub by Lifecycle-Innovations-Limited under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇