Commands

Usage stats for the obsidian-cli-mcp server (/cli-mcp-tool-stats): calls, estimated tokens, errors and latency per tool, with hints on heavy results, repeat calls, error patterns and unused schemas, kept across sessions.

A review desk panel (/reviews): Claude publishes open questions, decisions, findings, write plans, animated explainers and read-throughs; you answer, ask and submit in the panel, and the outcome goes back to Claude.

Live Claude + Codex quota band above the prompt: context, 5h and 7d windows, token counts, pace and a 7-day plan

Keep huge shell output out of the context window. A Bash result over a threshold is saved to a file and Claude gets its head and tail plus a slice tool to grep or page the rest on demand.

Connect Four against Claude, in a pane. Press a column's digit to drop a disc; Claude answers in half a second at three levels, from beatable to a seven-move lookahead. Zero tokens.

Limit which paths Claude may edit in a project with one /fence command. Edits outside the fence are refused with a reason Claude can act on.

2048 in a pane. Slide tiles with w, a, s and d, merge equal numbers, reach 2048. One undo, a best score that survives restarts, and a board that replays from its seed. Zero tokens.

Choose which MCP tools and subagent types Claude sees, per project. A pane lists every server and tool with the size of its description; defer or hide the ones this repo never needs and stop paying for them on every request.

Know whether your auto-memory index loaded whole. Reports the index's size against a limit you set at every session start, names the entries past the cut, and warns when a session pushes it over.

Memory pairs in a pane. Sixteen face-down cards, eight matching pairs; press a card's letter to turn it, find its twin, finish in as few turns and as little time as you can. Best of each kept. Zero tokens.

Hold npm, pnpm, yarn, pip, uv, and cargo installs of packages that don't exist, are brand new, or are barely downloaded, with the registry facts in the question. Catches hallucinated and typosquat packages before they land.

Run the project's tests after any turn that edited files, print pass or fail under Claude's answer, and send the failure back to Claude with one /fix command.

Put the file path on every Read, Edit, Write, Glob, and Grep row in the transcript, so you never expand a row just to learn which file it touched.

Snake in a pane. Steer with w, a, s and d, eat the food, don't hit the walls or yourself. Pause with p, pick the speed, high score kept. Zero tokens.

Sudoku in a pane. Three levels with one solution each, move with w a s d, type a digit, undo, a hint when stuck, and a clock that pauses when the pane closes. Best time per level kept. Zero tokens.

Check what Claude claims against what it ran. When an answer says the tests pass, the build is clean, or something was committed, a line under it says whether a matching command actually ran this turn and succeeded.

Typing race in a pane. A line of code appears, you type it; every character colors right or wrong as you go, and Enter scores words per minute and accuracy. Last ten runs and your best kept. Zero tokens.

Tic-tac-toe against Claude, in a pane. Press a digit to play a square; Claude answers in half a second at three levels, from beatable to perfect. Zero tokens.

Pane listing GitLab/GitHub issues assigned to me, grouped by board status label

The Awesome Statusline layout in a Status tab of the side pane, its bars upright, or as a band by the prompt: model, git, context, 5H/7D limits and Codex 7D

A pane that charts the tool calls of the turn as bars along its time, like a browser's network tab; opened and closed with /waterfall

SwitchMod: useful extras for Claude Code, each one a switch. A usage meter above the prompt, an output viewer for long results and images, secret hiding, a stop for repeated failures, a check before risky commands, a work log, and coordination between parallel chats. /switchmod turns each on or off.

A side chat in a pane that reads the main chat, scrolls and draws: /ask a question, /draw a diagram. Nothing goes back to the main chat unless you send it. Answers are Mermaid drawn as box art in the terminal and as SVG in the desktop app.

Replies that point at code: ask with /code-reference (a question, or a PR to review) and each place the reply names opens in a code pane beside it, the prose linked to it and boxed under each section. Only the command triggers it. Drawn the same in the terminal and the desktop app. PRs are read with gh, a GitHub MCP server or git, and checked out into a review worktree.