It runs inside the Claude Code process. The side panel is only what the author's README names. Read the repo before you install, or run claude plugin validate on the plugin folder.
Version
0.1.0
License
MIT
Repo stars
4
Last change
2026-10-01
What it can reach
Draws in the session
Calls another program on this machine
The exclude option skips projects whose paths hold that text; set your own, or set it later in /plugin configure. Claude Code 2.1.287 or later, and Node 18 or later on PATH for the scanner. Reports go to ~/.claude/mod-scout and quote 110-character prompt snippets while examples is on; turn it off before sharing one. The pane is not drawn over Remote Control.
The marketplace name is claude-code-mods. The marketplace also holds usage-meter, check-ledger, and resume-nudge, which the author chose with this one. This one installs on its own. The ranked list of mods for how you work is why this page files it under workflow. mod-store, by hellosverre, opens /mods, a pane to browse and install community mods. leaks, by davekiss, ranks the avoidable spend in the last 7 days of transcripts. This one counts what your transcripts show, repeated prompts, verify-style follow-ups, permission denials, Bash command families, and compactions, scores them against a catalog of mod shapes, and says which should not be mods. /mod-scout design 3 sends Claude one prompt to design the top three with the bundled design-mods skill and ask before building.
Demo
Screenshot of the author's GitHub page.
What it hooks into
session.startWhen a session starts
command.runWhen you run its slash command/mod-scout
ui.renderDraws into the sessionPane
Read from the on() calls in its hook modules. Open its source under Files to check what each one does.
Slash commands 1
/mod-scoutScan your recent sessions and rank the mods you would use most
Files
The author's README and source, 4 files. They load when you open them.