Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add boshu2/agentops --skill account-rotationgit clone --depth 1 https://github.com/boshu2/agentopsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/boshu2/agentops/account-rotation)<a href="https://agentmods.dev/skills/boshu2/agentops/account-rotation"><img src="https://agentmods.dev/badge/skills/boshu2/agentops/account-rotation.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00030 | $0.00561 |
| Opus 5 | $0.00015 | $0.00280 |
| Sonnet 5 | $0.00006 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
account-rotation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Account rotation — credential adapter
Choose the credential tool from both host and agent family, perform only the explicit account switch, and report the identity observed by the matching runtime.
Verifying identity through the target runtime works because the runtime is the only party whose opinion matters: credential files can be swapped perfectly and still authenticate as the old account in an already-running process.
Named failure mode — stale-process identity: declaring the rotation done while every live session still holds the previous account's tokens in memory.
Anti-pattern: confirming a switch by diffing credential file bytes. Corrective: ask the matching runtime who it is now, and report whether a new process is required for the answer to hold.
Boundary
- Perform only the account switch the caller explicitly authorized; rotation mutates host credential state and is never implied by repository access.
- The credential tool is caller- or operator-selected per host and agent family;
the names below are this operator's routes, not a universal prescription. On
macOS with Claude credentials the route is
claude-acct(Keychain-backed); file-backed Codex, Gemini, Linux, or WSL credentials usecaam. Never usecaamfor macOS Claude account operations. - Verify account identity through the target runtime; token bytes are not account identity.
- If neither the selected credential tool nor a runtime identity probe is available, report that absence as a disclosed fact and stop. Never fall back to diffing credential-file bytes to declare a switch done.
- Existing processes retain credentials already loaded in memory. Rotation affects a new process.
- This skill does not restart work, resume a task, select a pane, move repository state, or decide what happens after the switch.
Return the host, agent family, selected tool, requested account/profile, the identity observed before and after the switch, whether any live runtime still holds the previous account (a partial rotation), the command exit code, and whether a new process is required for the new identity to hold.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 61 lines · 30 tokens per session scan A 91d38d0f1b31
account-rotation is a skill published in the GitHub repository boshu2/agentops (433 stars, last pushed today), licensed Apache-2.0. It adds 30 tokens to every session and 561 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
brainstorm
Explore vague or ambitious ideas into a right-sized requirements-only plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning, not for a decisive verdict on whether to adopt or switch to a specific external technology, library, or…
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
commit-push-pr
Use when asked to commit, push a feature branch, and open or update a pull request with gh in one pass. Not for a push with no PR: use commit-push. Not for a PR body alone: use create-pull-request.
commit
Use when asked to commit changes, create a typed branch, format history for a changelog, or rewrite messages of HEAD or an unpushed range. Not for pushing or a PR: use commit-push or commit-push-pr.
deps-upgrade
Use when dependency upgrades need batching for CVEs, a major release, forced compatibility, a scheduled or vulnerability-triggered sweep. Not for PR queue triage: use github-backlog-triage.
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project. For doc-vs-code drift inside a specific diff, use sync-docs.