Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jtsternberg/claude-plugins/plugin install gwsWrote 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/jtsternberg/claude-plugins/account)<a href="https://agentmods.dev/skills/jtsternberg/claude-plugins/account"><img src="https://agentmods.dev/badge/skills/jtsternberg/claude-plugins/account.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.00036 | $0.02118 |
| Opus 5 | $0.00018 | $0.01059 |
| Sonnet 5 | $0.00007 | $0.00424 |
| Haiku 4.5 | $0.00004 | $0.00212 |
Grade A, and why
gws-account 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 6d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Account Manager
Manage multiple Google accounts for use with the gws CLI. Each account
is stored in its own config directory under ~/.config/gws-accounts/<label>/.
Prerequisites
# Codex: this path resolves under Claude Code; substitute the directory containing this plugin.
PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT}"
bash "$PLUGIN_ROOT/scripts/auth-preflight.sh"
Read that output carefully — it distinguishes three states that a plain
gws auth status check conflates:
| Output | What it means | Fix |
|---|---|---|
Authenticated as: X (account: <label>) |
Ready | — |
Same, plus a Note: no account is selected block |
Calls are silently going to the default config while other authed accounts exist | account-switch.sh <label> |
ERROR: no account is selected and the default config has no credentials |
Nothing selected, default is empty, but other accounts are authed | account-switch.sh <label> — not gws auth login |
ERROR: the selected account '<label>' no longer exists |
.active names a directory that is gone |
account-switch.sh <label> (or re-add it) |
ERROR: gws has no stored credentials for any account |
Genuinely unauthenticated | gws auth login |
That fourth row is a hard stop on purpose, even when the default account is authenticated: continuing would run as an identity you didn't select. The selection file is left in place rather than "self-healed" away — deleting it would erase the only evidence that anything was wrong and make the next run look normal while acting as the wrong account.
Never re-run OAuth on the strength of a failed gws auth status alone. gws
writes Using keyring backend: keyring to stderr on every call, so any check
that merges stderr into a JSON parser reports a false negative every time.
Task
Parse the user's request to determine which subcommand to run, then execute the appropriate script.
Add a new account
# Codex: this path resolves under Claude Code; substitute the directory containing this plugin.
PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT}"
bash "$PLUGIN_ROOT/scripts/account-add.sh" <label>
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.
- 6d ago First seen · 207 lines · 36 tokens per session scan A 3a6d6294970b
gws-account is a skill published in the GitHub repository jtsternberg/claude-plugins (5 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 2,118 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…