Mods and a status line for Claude Code. A reply's diagrams, formulas, images and videos are drawn as pictures in the terminal, its markdown is drawn in color, background shells, test runs and a turn's edits get views of their own, and the status line says what the session is costing.
| Path | What it does |
|---|---|
mods/reply-media/ |
Draws mermaid fences, formulas (math fences and $$ blocks) and local images ( on a line of its own) as pictures. A local video written as an image is drawn as its first frame with a play button, and plays in place. Under each picture, one button copies its source and one opens it larger in a pane. |
mods/reply-markdown/ |
Draws headings, lists, task lists, quotes, callouts (> [!WARNING]), rules and tables in color, and puts each code fence in a card with a copy button. |
mods/skill-router/ |
/skill-router <question> asks a small model which of your user-only skills fits the question. With no question it lists them. |
mods/shell-tail/ |
Lists every shell running in the background in a band above the prompt, Claude's or a ! command you sent there with ctrl+b, named by what it does: how long it has run, how many lines it wrote, its last line, and a button that stops it. A command in the foreground is left to the transcript. |
mods/test-summary/ |
Draws a test or type-check run (node --test, bun test, claude plugin test, cargo test, go test -v, pytest, vitest, jest, tsc, and the compact form RTK rewrites each to) as one count line with each failure and its error under it. The passing tests, a copy of the failures and the whole output are a press away. |
mods/turn-changes/ |
Lists the files the last turn changed in a pane, each with its diff a press away: its edits, and in a git repo what its commands changed. /changes opens it; with autoOpen on, it opens by itself at a turn's first edit where the terminal is wide enough. |
statusline.mjs |
The status line. First row: context used, cost, model, tokens per second, folder, cache hit rate, git state. Second row: subscription windows and when they refill, Remote Control, and the other sessions running on the machine. |
Headings, lists, a quote, a rule, and bold, italic and inline code:
The five callouts:
A table, a task list, and a code fence as a card with its copy button:
Bold in Chinese is drawn bold where it ends in a full stop or a bracket. CommonMark leaves **收斂。**記憶 as written, its asterisks showing, since Chinese sets no space after its punctuation; the mod moves that punctuation outside the ** (**收斂**。記憶), which reads the same.
A dev server left running in the background, a failing test run, the fix, and the run again:
shell-tail: the band above the prompt, one row per background shell, its dot in the theme's color for background work.test-summary: the count line underRan 1 shell command, each failure and its diff under it.turn-changes: the pane on the right, opened here by the turn's first edit (autoOpenon), else by/changes. A press on a file shows its diff.
- Claude Code with the mod API (function-hook plugins). The API is early access and may change under these mods. Last run on Claude Code 2.1.304.
- macOS. The picture scripts call
sipsandopen. - For
reply-media, a terminal that speaks the kitty graphics protocol: Ghostty or kitty. - Node.js, and for
reply-media:
brew install librsvg ffmpeggit clone https://github.com/NateCC0902/NeonCoat.git
cd NeonCoat/mods/reply-media/render && npm installThen point ~/.claude/settings.json at the clone. CLAUDE_CODE_PLUGIN_DIRS is colon-separated with one entry per mod (a parent folder is not scanned), so leave out the mods you do not want:
{
"env": {
"CLAUDE_CODE_PLUGIN_DIRS": "/path/to/NeonCoat/mods/reply-media:/path/to/NeonCoat/mods/reply-markdown:/path/to/NeonCoat/mods/skill-router:/path/to/NeonCoat/mods/shell-tail:/path/to/NeonCoat/mods/test-summary:/path/to/NeonCoat/mods/turn-changes"
},
"statusLine": {
"type": "command",
"command": "node /path/to/NeonCoat/statusline.mjs",
"padding": 0,
"refreshInterval": 5
}
}The mods load in sessions started after that. These files are loaded live from the clone: a saved mod file hot-reloads in running sessions, so a broken edit breaks the terminal UI of all of them.
reply-media draws only what Claude writes in the forms it knows: a mermaid fence, a math fence, an image on a line of its own. Claude does not write them unprompted, so the mod tells it: it adds a note to the system prompt (forms in mods/reply-media/hooks/register.tsx). reply-markdown does the same for the forms it draws only when Claude chooses to write them: alerts, task lists, and a code fence for what you will copy. A note is added only where a reply is drawn on a terminal, not under claude -p or in an app, where the forms would come out as their source; a mod turned off adds none, and a form switched off in /config is left out of it. There is nothing to put in your CLAUDE.md.
Each mod's options are rows in /config, and a change takes effect at once. Every feature has a switch of its own: one turned off is drawn by Claude Code as it would be without the mod.
| Mod | Option | Default | What it changes |
|---|---|---|---|
| all six | enabled |
true |
Turns the mod off without removing it. |
reply-media |
diagrams, math, images, videos |
true |
Draws mermaid fences, formulas, local images, local videos. Off, that kind stays text, and Claude is not told to write it. |
reply-media |
buttons |
true |
The copy and zoom (a video's open) buttons under a picture. |
reply-media |
pxPerColumn |
8 |
Pixels of a picture per terminal column. Lower draws pictures larger. |
reply-media |
cellAspect |
2.17 |
How many times taller than wide one terminal cell is. Change it when pictures look squashed or stretched. |
reply-media |
resumedReplies |
3 |
How many of a resumed session's last replies get their pictures drawn again. |
reply-markdown |
headings, lists, quotes, callouts, tables, rules, codeCards |
true |
Restyles that kind of block. Off, Claude Code draws it, and Claude is not told to write alerts (callouts), task lists (lists) or a fence for what you will copy (codeCards). |
reply-markdown |
tableBorder |
rules |
rules: no frame, a line under the header and a faint one between the rows. Or a frame: round, single or bold. |
reply-markdown |
cardBorder |
round |
The border of a code card and of a callout box: round, single or bold. |
shell-tail |
rows |
5 |
The most rows the band takes. Past it, the newest shells are counted on one row: +N more. |
test-summary |
nodeTest, bunTest, cargoTest, goTest, pytest, vitestJest, tsc |
true |
Summarizes that runner's output, and RTK's form of it (bunTest covers claude plugin test too, vitestJest both). Off, Claude Code draws it. |
test-summary |
failureLines |
12 |
How many lines of each failure's error are shown. copy failures copies them all. |
turn-changes |
bash |
true |
Lists what a Bash command changed too, from a snapshot of the git repo before and after it. Off, only Edit and Write are listed, and a command runs without the two snapshots. |
turn-changes |
autoOpen |
false |
Opens the pane at a turn's first edit, where the terminal is wide enough. Off, /changes opens it. |
The colors are written into the code to match one dark theme, which is not in this repo. For another theme, edit the constants at the top of each file: COLORS in statusline.mjs, COLOR and CALLOUT in mods/reply-markdown/hooks/register.tsx, and THEME in mods/reply-media/render/render.mjs. shell-tail, test-summary and turn-changes name the theme's own colors (background, success, error, subtle), so they follow whichever theme is set.
Run these after a change, from the repo's root:
claude plugin validate mods/<name> && claude plugin test mods/<name>
npx -p typescript tsc -p mods/<name>
(cd mods/reply-media/render && npm test)
echo '{}' | node statusline.mjs && node --test statusline.test.mjs
e2e/<name>.sh # shell-tail, turn-changes, test-summary, reply-markdown: a real session in tmux, a few haiku turnsThe types check works once Claude Code has loaded the mod and written its types to mods/<name>/.claude-plugin/types/. CLAUDE.md has the notes for changing or adding a mod.




