Claude Code mod
spick-dashboard
Shows who is working now (lane, model, the main loop's prompt size) above the prompt, and a /spick pane with switches (routing, review, gate, guard, lanes, band), lane totals, local quota with each sample's age and recent turns. The switches shape the per-prompt triage checklist, which carries a keyword Hint line per prompt. Enforcement is on facts: the guard lets the main session edit one source file per turn (the second goes to a coder) and sends a turn back once when source was edited and no check passed after the last edit; the gate sends a turn back once when a hinted verdict's role (deep for judgement, the review lane or deep for review) did not complete and no Kept: line says why; both reasons go back in one block. A check that fails twice in a turn adds an escalation line; a coder, planner or deep call with no effort gets the default; a Haiku session past 80k tokens is warned. Each main turn is one JSON line in <config>/spick/turns/<session>.jsonl; /spick spend and /spick audit report on them.
Install
/plugin marketplace add Brulek/spick
/plugin install spick-dashboard@spickMods install like plugins. Run /reload-plugins or start a new session to load it.
What it can access
- Reach
- L2Writes or runs: runs processes, writes files, reads files, reads env vars, reads mod state, persists state, draws
- Sees
- every prompt, every tool call, Agent calls, subagent spawns, Bash calls, Edit calls, Write calls, NotebookEdit calls, classic hooks
- Draws in
AbovePromptPane- Hooks
session.startprompt.submitcommand.runconfig.setprompt.composeturn.startturn.steptool.callagent.spawnclassic.Stopturn.completeui.render
From a static scan of the mod's code by awesome-claude-code-mods. It shows what the code asks for, not a security review.
How Claude Code mods work
- A mod is a plugin with a JavaScript or TypeScript module that runs inside Claude Code (version 2.1.287 or later). It can draw panes beside the transcript, a band above the prompt, buttons and toasts, restyle the spinner and tool rows, and watch or rewrite tool calls and prompts.
- It installs like any plugin: add its marketplace with /plugin marketplace add owner/repo, then /plugin install name@marketplace.
- Check what a mod can reach before installing: it runs with your permissions. Reach goes from drawing only, to reading files, to writing files or running processes, to the network. Run claude plugin validate on a clone to list its hooks and calls without running it.
- Turn one off from the Installed tab in /plugin, or start Claude Code with --safe-mode to skip every customization for a session.
Details
- Repository
- Brulek/spick
- Folder
mod/spick-dashboard- Marketplace
spick- Author
- Brulek
- License
- MIT
- Last updated
- 28 October 2026
- Listed in
- awesome-claude-code-mods
FAQ
What is spick-dashboard?
Shows who is working now (lane, model, the main loop's prompt size) above the prompt, and a /spick pane with switches (routing, review, gate, guard, lanes, band), lane totals, local quota with each sample's age and recent turns. The switches shape the per-prompt triage checklist, which carries a keyword Hint line per prompt. Enforcement is on facts: the guard lets the main session edit one source file per turn (the second goes to a coder) and sends a turn back once when source was edited and no check passed after the last edit; the gate sends a turn back once when a hinted verdict's role (deep for judgement, the review lane or deep for review) did not complete and no Kept: line says why; both reasons go back in one block. A check that fails twice in a turn adds an escalation line; a coder, planner or deep call with no effort gets the default; a Haiku session past 80k tokens is warned. Each main turn is one JSON line in <config>/spick/turns/<session>.jsonl; /spick spend and /spick audit report on them. It is a mod for Claude Code, from Brulek/spick on GitHub.
What can the spick-dashboard mod access?
Its widest reach is "writes or runs" (runs processes, writes files, reads files, reads env vars, reads mod state, persists state, draws). It sees every prompt, every tool call, Agent calls, subagent spawns, Bash calls, Edit calls, Write calls, NotebookEdit calls, classic hooks. It draws in AbovePrompt, Pane. Like any mod, it runs with your permissions.
How do I install spick-dashboard?
Inside Claude Code (v2.1.287 or later), run /plugin marketplace add Brulek/spick and then /plugin install spick-dashboard@spick.
More pane & dashboard mods
speckit-companion
alfredoperez/speckit-companion-claude-mod
Follow a Spec Kit run from inside Claude Code: a band above the prompt with where the run stands, a pane with the steps, their times, the documents and the tasks ticking off, and /speckit-tracker to switch specs. Press Enter to read a step's document, o to open it in your editor. Works with stock Spec Kit. Read only.
sprout
Tum4s/sprout
Subagent tracker: a band above the prompt and a panel with each agent's work and the files it touches
spec-flow
japan-da-man/claude-code
[mod] [skills] Turns a feature request into a spec, one approved step at a time: clarify the request (asking you what is unclear), survey every affected screen and feature with subagents, write the requirements, then propose several feature and UI options with mockups. Saved under docs/specs/; /specs shows the checklist
squishys
Rahat-ch/squishys
A companion mod for Claude Code's agents: every agent gets its own tiny pixel-art squishy you can watch, stop, redirect and collect.
spec-band
mercynet/my-claude-mods
A band above the prompt showing the active spec of the current branch: task progress, STATE.md age and phase, and a warning when STATE.md has not been updated for many edits.
staff-board
Gooner44/ClaudeMods
A compact band of your sessions (Claude, Aesop, named desktop sessions and what they spawn): Clawds coloured by model, glowing by effort, each with its current work
Browse the most popular Claude Code mods, all pane & dashboard mods, or the skills and MCP server directories.