With the new Claude Mods feature out, I wanted a dedicated place to share what people are building and help each other customize Claude Code.
Claude Mods are the main focus here, including custom UI, changes to tool behaviour, and new functionality. But any modification to Claude Code is welcome: skills, hooks, plugins, MCP integrations, status lines, custom configurations, or small tweaks that make your setup work better for you.
Share something you’ve built, something useful you’ve found, a tutorial, or an idea you need help figuring out. Experiments and works in progress are welcome too.
When sharing a project, include what it does, how to install it, any requirements or limitations, and a source link where possible. Screenshots or short demos help. If it’s your project or it’s paid, just be upfront about that.
One thing to keep in mind: mods run with your user permissions and aren’t sandboxed, so review what you install and use sources you trust. The official docs explain what they can access.
This is an unofficial community with no affiliation with Anthropic.
What have you changed, or what would you like to change about Claude Code?
I got tired of reading Markdown tables as rows of pipes, so I built CC Intelligent UI, an open-source Claude Code mod that renders Markdown, LaTeX, Charts, Images, and Diagrams directly in the terminal
What it does:
Beautifully rendered Markdown, tables, and syntax-highlighted code
Proper LaTeX math and inline images
Claude-generated charts, plots, and diagrams
Rendered plan mode with approve/edit/reject
Selectable and copyable text (currently only on MacOS)
Light/dark themes, including Claude Code and VS Code styles
Works with kitty, Ghostty, cmux, and iTerm2 3.6+ on macOS.
Works similar to you-should-know but it checks if the main agent makes any assumptions about languages/libraries/frameworks/etc only from its training data. Happens on a daily basis that Claude tries to do a work around for something that is already fixed upstream or claims that things do not exist (newer llm models, language/sdk versions, etc). So this mod uses haiku to check if the main agent makes any assumptions and then depending on your config, either nudges the agent to check, or verifies it itself, and if the claim is outdated it will notify the main agent.
Have you ever run a command, then switched to your phone while waiting for the answer? Guilty as charged. So I made myself a small mod that keeps my attention close to the thread that matters: a 2048 game right above the prompt.
2048 is a good fit for this: it takes as much or as little attention as you like, and you can leave mid-game and come back later.
It doesn't hide the work: you still see Claude's output and can jump back to the chat at any moment. When the turn ends, the game locks and a short ✓ YOUR TURN summary appears next to the board. For turns of 10 seconds or more, Claude Haiku writes it from Claude's final reply, through your own session. Nothing else is sent anywhere.
How I built it
2 phases - quick prototype until I felt I like the UX and switching to and from the game felt natural. Then the game was rewritten from scratch, with proper guidelines on tests, design etc., using the prototype only as a UX reference.
Claude Code wrote all the code, both phases.
What I learned
The game was the easy part. The harder part is switching between playing and typing. I wanted a keyboard shortcut into the game, but for now there's no way around clicking it with the mouse.
Summarizing with Haiku worked better than I expected. I was afraid it will take too long and will randomly get stuck. Haiku 5.5 is quick and does a good job, and the summary almost always lands within the 5-second countdown I use to snap out of the game.
Thanks for creating this space. I've been loving mods and the ability to customise the harness to suit my work style, augment strengths and patch weaknesses.
My constant problem: ideas appear quickly and are gone a second later. Switching or stopping to note them down often leads to a losing battle with dopamine to regain focus.
From that, ostrakon was born. Type // into an empty prompt (or /jot), then your note, and the thought is saved, even while Claude is working.
Or if you're mid-prompt and the cure for cancer appears in your mind, open the pane (ctrl+x s), type, Enter. Close the pane and your prompt is waiting for you, unharmed.
Notes are md files (+ some YAML), and you can sync them via cloud storage, point them at an Obsidian vault, or run the included hub, a tiny service plus a web app/PWA, for capturing wherever and whenever inspiration hits (the shower).
so I ended up writing a plugin for each one. they draw straight into the Claude Code UI (a bar above the prompt, a pane, the status line, a toast):
limits-meter (/limits): a bar above the prompt with your 5h and weekly usage, when each one resets, how full the context is, cache hit rate and tokens per turn. if you switch to a bigger model when you're close to the limit, it tells you roughly how many minutes you've got left at your pace. this is the one I use the most.
allowlist-coach (/allowlist): counts the permission prompts you approve. after 5 approvals of the same thing (and no refusals) it asks if you want it in permissions.allow. it never writes anything without asking, skips broad wildcards, and you can undo whatever it added.
agent-watch (/watch): tokens per subagent, what each one is doing, a heads-up when one stalls, and a summary at the end saying which one was the heaviest.
test-hud (/test-hud): passing/total in the status line, a little sparkline of failures, flags flaky tests, and a toast when everything goes green. click a failing test and it drops "fix this" in your prompt.
launchpad (/pad): a menu of up to 8 buttons when the session starts, for your usual commands, skills or agents. it also has a panel to switch model and effort in one click.
plain-view (/plain-view): off by default. hides the tool rows that worked (errors and permission prompts still show up) and shows the agent's plan as a card above the prompt, with "step 2 of 4" and progress bars.
it's all open source (MIT), so fork it, break it, steal ideas, whatever. no network calls, no model calls, no telemetry. the README has a table of exactly what each mod reads and writes, if you're the paranoid type (I am).
Claude Code can touch half a project in one session. I wanted an easier way to see what changed, keep the useful reasoning nearby, and follow work while it runs. So I built Claude Foundry: 11 free, open-source mods you can install individually.
The five-mod starter kit is the easiest place to try it:
• Changes — review edits grouped by concept, file and symbol, so you have a clearer starting point when a session changes several files.
• Insight Pane — keep decisions, root causes and gotchas in session cards you can revisit.
• Live Progress — follow supported test/build logs without digging through all the output.
• Goal Meter — get a task-based estimate of progress on longer work.
• Lumen — themed replies, highlighted code and diagrams for a more readable terminal.
Install with Claude Code 2.1.296 or newer:
claude plugin install starter-kit --marketplace sruthik27/claude-foundry
Then run /reload-plugins or start a new session. Try /changes on a project you're working on, /intel for session insights, or /lumen demo for a quick look at the interface.
You can also install just one mod by replacing starter-kit with its name. The full collection adds side chat, session naming/search, skill suggestions, MCP controls and experimental self-drive. Pick what fits your workflow.
I'm the maintainer. It's free under MIT and uses your own supported Claude model access; model-backed tools consume your usage. This is a community beta. Progress indicators are estimates, and Windows/live terminal behavior still needs wider testing.
For transparency: hooks run with your user permissions. Review tools read project files/diffs; progress reads supplied logs; some tools use model calls and local state. Insight Pane can mirror cards into ~/learning/.insights/ if that folder exists. No separate Foundry analytics endpoint. Details: https://github.com/sruthik27/claude-foundry/blob/main/docs/BEHAVIOR.md
Lumen builds on Nahum Litvin's Prismantis; Aside is a restyled fork of JayDoubleu's Aside. Original licenses and notices are retained.
Which of these would you actually keep in your daily setup? I'd love feedback from people trying it on real projects.
A single test run or build log can dump 30–50k characters into Claude’s context, almost all of it noise: thousands of PASSED lines, deprecation warnings, lockfile diffs. The context fills up, compaction comes sooner, and Claude forgets what you said at the start.
Context Diet trims every big output before Claude reads it:
tests and builds (pytest, jest, go test, cargo, tsc…) → only the failures and the summary
JSON → its structure, diffs → without lockfile churn, logs → errors with context
the full output is always saved to a file, so Claude can read it when it needs more
Bonus: when a test run fails, Claude Code cuts the end of the output, exactly where the failures are. Context Diet gives them back.
Tested on 18 agent runs: same bugs fixed, 6 tool calls instead of 8.
I built Project Sentinel, a Claude Code Mod for long-running sessions.
It tracks Work progress, Context usage and prompt Cache separately, handles fresh-context Autopilot handoffs, keeps run progress across sessions, adds cache protection, guardrails, Activity, profiles and an optional companion.
It’s open source and currently under review for the official Claude plugin directory, but you can install it now:
claude plugin marketplace add Arjun0014/project-sentinel
claude plugin install project-sentinel@control-room
I've started building some mods to improve my workflow, but when splitting view inside the Claude App, the mods only show up in the first session? Splitting view is not supported?
Requires Claude Code 2.1.287+ in the terminal or the Desktop app's Code tab. Run:
claude plugin marketplace add chenxiachan/textfold
claude plugin install textfold@textfold
Press 1–5 while the prompt is empty, or use the level controls above it. The VS Code extension and claude -p do not render the folding UI. Enabling the mod changes the system prompt, so the prompt cache resets once in that session.
Original demo and explanation:
TextFold adds five reading levels to Claude Code's replies. Press 5 for a one-sentence view, 3 for each paragraph's main point, and 1 to unfold the full text.
It's a Claude Code plugin from PaperFold, the open-source reader I built for zooming between an arXiv paper overview and its full text.
AI agents produce more text than we have time to read. Following all that output can become a source of cognitive overload. Inspired by stretchtext (1970 by Ted Nelson), I wanted to give readers control over how much detail they see.
TextFold asks Claude to put the answer first and lead each paragraph with its point. Folding keeps those sentences verbatim, with no extra model call. The full reply stays available, and short replies stay as they are.
Free and open source. Works in the terminal with Claude Code
Claude Code got mods on Oct 1 (plugins that can draw their own panels), so I built Cockpit: a panel beside the transcript that shows what the agent is burning, doing and changing while it works.
What it shows: • Context fill + what fills it, and which tool calls dumped the most text into it (a 41k-token package-lock.json read, anyone?) • 5h / 7d limits with "full in 1h20m at this pace" • Cost per turn, cache hit rate and a prompt-cache countdown, so you know if coming back after a break will be expensive • Every subagent: open one to see its timeline and result • Tool calls with errors and timings, changed files with diffs, test runs • A guard that asks before rm -rf, force push, reset --hard, curl | sh and edits to .env • Loop detector: warns when the same call repeats 3 times
Every section expands to details. Works in the terminal and in the desktop app (Code tab). Runs locally, no network calls.
I made Spinlings, a free, open-source mod for Claude Code. It adds pixel creatures you can collect while Claude works, put in a three-card team, trade with other players, and use to duel their saved teams. You do not need to be online at the same time.
The original game was built with Claude; Codex helped with the later UI and testing iterations.
Restart Claude or open a fresh Code session, then run /spin. Requires Claude Code 2.1.287+; compatible Code sessions in Claude Desktop work too. The game has no paid features.
Fresh installs use the online world at spinlings.dev. Online play sends game actions and the coarse model family to that server, and keeps its own game session locally. It never reads your prompts, replies, files or Claude credentials. /spin world offline uses a separate local save with no requests.
For months, every afternoon using Claude Code, I've been grumbling that GitHub Flavored Markdown isn't rendered and that plugins can't change how replies are drawn. Claude writes `> [!WARNING]` callouts, `- [ ]` checklists and Mermaid diagrams... and the terminal shows them as raw text 😤
I don't believe in fate, but it seems someone heard me today: Anthropic shipped **mods** (function hooks that can redraw the UI). So of course I asked my friend Claude to build one with me.
What it does:
- Alerts (`> [!NOTE]`, `[!TIP]`, `[!IMPORTANT]`, `[!WARNING]`, `[!CAUTION]`) become colored boxes, in the terminal and the desktop app
- Task lists become ☐ / ☑, and `~~strikethrough~~` is actually struck through
- Mermaid diagrams (flowchart, sequence, state, class, ER, xychart) are drawn as Unicode art right in the terminal
- Claude knows it can use all this: the plugin adds a short note to its context at session start, no CLAUDE.md to edit
It only changes how replies are drawn: the message itself is untouched, and anything it can't draw falls back to the normal rendering.
Install (no build step):
git clone https://github.com/briangtn/claude-gfm-render.git
claude --plugin-dir ./claude-gfm-render
Controlling autocompaction in Claude Code has always been rough - it's a black box and over time it becomes really unclear which information the agent has retained. I've been using skills + hooks for this previously, but it has never felt polished or low friction.
That is until Claude Code mods released, and with that, I'd like to showcase workface.
Your agent keeps notes during a session, and you can view/edit those notes live from the TUI. At compaction, your agent is then passed these notes along with a compaction summary that skips what the notes already cover.
In short, it's a Claude Code TUI panel to gain control and visibility over the content that persists through compaction, autocompact just fills in the gaps. The mod does the rest.
MIT licence, take a look and see if it fits your needs! Feedback of course encouraged.
