SimpleCORE Claude Mods

Plugins for Claude Code that add panes, a status band and slash commands to the terminal: switch between several Claude accounts, watch their usage limits and token use, see and clean up what Claude Code keeps on the machine, and keep agents, worktrees, checkpoints, diffs and memory files in one pane, and run a project's builds and commands from buttons. Install one plugin, sc, and you get them all.

Important

Clicking needs Claude Code's fullscreen mode. The buttons, tabs, tiles and status band cells answer a mouse click only while Claude Code draws in fullscreen mode. Turn it on once with /tui fullscreen, which is kept as "tui": "fullscreen" in ~/.claude/settings.json. In the default mode Claude Code passes no click to the plugins, on every platform, Windows and WSL included. See Clicking and the keyboard.

What's inside

Accounts · /sc:accounts

• Keep several Claude logins and switch every running session to another in one step.
• See each account's five-hour, weekly and per-model usage, with reset times, and what it spent past its plan when Claude reports it.
• See the Codex login the session's Codex uses, with its limits and credits, on a card of its own where the Codex CLI is installed.
• Usage: the tokens used on this machine by day, model and project, counted from Claude Code's transcripts.
• Storage: what ~/.claude holds by kind and project, and a cleanup of idle sessions confirmed by typing a word.
• A status band above the prompt: account, model and effort, task, context and usage, branch and PR, lines changed. Press the account's name to open the accounts pane, or the branch or the lines changed to open the workspace.
• Each subagent's model and effort after its task in Claude Code's agent list: Review auth · Opus 5.5 (high).
• Where the Codex CLI is installed, OpenAI Codex as a subagent: Claude starts it with the Agent tool (sc-accounts:codex-read, codex-write, codex-run) and sc-accounts drives codex app-server in its place.
• An optional webhook sends the status to an external system. It is off by default; leave it off if you have nothing to send to.

Workspace · /sc:workspace

• Agents: the session's subagents, what each did last and the answers of those that finished, and the repository's worktrees; stop an agent, open a worktree's changes, remove a merged one.
• Checkpoints: a snapshot of the working tree before every prompt; compare with one, see one turn's changes, name and pin one, or restore it.
• Notes: numbered notes kept per project, optionally sent to Claude with every prompt; Claude can mark one done for you to confirm.
• Diff: the files changed since the session started or since a checkpoint, up to now or a later checkpoint; each file's diff, restoring one file, and a request for a commit message.
• Memory: the memory files Claude Code reads, global and project apart, to read as Markdown and search line by line.

Toolbox · /sc:toolbox

• The project's commands as buttons of one size, from ⚒ Toolbox on the status band.
• Run and stop shell commands, and watch their log live in a dialog.
• Add tasks found in npm, Vite, Maven, Gradle, Cargo, make, just, Compose, Go and Python projects, or Claude's own commands such as /clear and /compact.
• Values fixed or asked at each run, with paths completed as you type.
• Kept in .toolbox/toolbox.json in the project; share it or ignore it in git. A skill lets Claude write it for you.

Anything that cannot be taken back asks in a dialog first; Esc cancels.

Clicking and the keyboard

Requirement	Why
Claude Code in fullscreen mode: /tui fullscreen, or "tui": "fullscreen" in ~/.claude/settings.json	Only the fullscreen mode reads the mouse; in the default mode no click reaches a plugin
A terminal that passes mouse events to the program running in it; inside tmux, set -g mouse on	A terminal that keeps the mouse for its own text selection sends Claude Code no click to pass on

Without a click, every control is reached from the keyboard:

• ctrl+x then Tab gives the open pane, or the status band, the keyboard.
• Tab and the arrow keys move between buttons; Enter presses the one with the ring.
• A digit picks a tab; Esc goes back from a dialog and closes a pane.
• Every pane also opens from its command: /sc:accounts, /sc:workspace, /sc:toolbox.

The first pane a command opens outside fullscreen mode says so in its reply.

In the Claude desktop app the panes and the band draw with the app's own buttons, tabs and font: rows wrap by the app's measure rather than the terminal's cells, the Usage chart is a picture, and a pane closes from its own title bar.

Install

claude plugin marketplace add simplecore-inc/claude-mods
claude plugin install sc@simplecore-mods

sc installs sc-accounts, sc-workspace and sc-toolbox with it. The plugins are installed for your user, so they run in every session. Run /reload-plugins in a session that was already open.

To use a local clone instead, add its folder as the marketplace:

git clone https://github.com/simplecore-inc/claude-mods.git
claude plugin marketplace add ./claude-mods
claude plugin install sc@simplecore-mods

Update

claude plugin marketplace update simplecore-mods
claude plugin update sc@simplecore-mods
claude plugin update sc-accounts@simplecore-mods
claude plugin update sc-workspace@simplecore-mods
claude plugin update sc-toolbox@simplecore-mods

Then run /reload-plugins in each open session. With a local clone, git pull in the clone and /reload-plugins are enough: a plugin from a folder marketplace is read from that folder.

Uninstall

claude plugin uninstall sc@simplecore-mods
claude plugin prune
claude plugin marketplace remove simplecore-mods

prune removes sc-accounts, sc-workspace and sc-toolbox, which were installed as dependencies of sc; uninstall them by name instead if you installed them yourself. marketplace remove is only needed when you will not install from it again.

The mods leave some data behind, which you can delete by hand:

What	Where
Saved logins	macOS: keychain items of the service account-switch. Elsewhere: ~/.claude/account-switch/
Webhook token	macOS: the keychain item of the service sc-webhook. Elsewhere: ~/.claude/sc-accounts/webhook-token
Webhook template	~/.claude/sc-accounts/
Settings, account index	~/.claude/plugins/store/sc-*.json
Tools, their logs and remembered values	in each project: .toolbox/
Notes and checkpoint lists	in each repository's git folder: .git/sc-workspace/, a pair of files per worktree
Checkpoints	in each repository: the refs under refs/sc/, and the files sc-snapshot-*.index in the git folder and in each worktree's folder under .git/worktrees/

~/.claude is CLAUDE_CONFIG_DIR when that is set. To delete a repository's checkpoints, and its notes with them, run in the repository:

git for-each-ref --format='%(refname)' refs/sc/ | xargs -n 1 git update-ref -d
common="$(git rev-parse --git-common-dir)"
rm -f "$common"/sc-snapshot-*.index "$common"/worktrees/*/sc-snapshot-*.index
rm -rf "$common/sc-workspace"

The account you are logged in with stays logged in; only the saved copies go.

Language

The mods show English, and Korean where Claude Code's language setting is Korean; any other language falls back to English. Without that setting, LC_ALL, LC_MESSAGES and LANG decide, in that order.

Developing

Developing a mod covers the layout, the rules the engine enforces, the checks and how to release.

License

MIT