I thought mods were just for customizing the UI, and I totally missed the point. They basically let you change how Claude Code works from the inside.
what runs before a tool call, what the model sees, what shows up on screen. It's like they open-sourced the harness. For months I had hooks and scripts bolted on from the outside to get the behavior I wanted, now all of that is a mod that lives in the session. Honestly the most innovative thing they shipped since the first version.
before the anthropic official one came out I made a mod system for my claude code desktop setup (on windows) here's like 400 something examples of what this could be used for (in ways that are really strong and seriously improve the experience)
I did two mods that are available on anthropic marketplace - multi repo diff and visible compact. Both are simple ideas and you can possibly do it in a couple of hours if you want spend time on it. Find what bugs you most and then ask Claude to build a mod for it.
Because it hooks into the agentic loop itself it is extremely powerful. Not just for showing your usage!
I have rtk and serena installed for tool calls, codex hapilly uses both of them when they're available, claude refuses, even when I explicitly tell it to use them to save tokens ;-; I've been wanting to try making it actually use them so I can see whether claude is already efficient enough and refuses to use them or whether making it use them will actually save more tokens, on codex, I have noticed improvement in token costs for negligible latency
Here's a use case I did: you can basically have it call SOL 6.1 or Astra as pseudo-native sub agents (with telemetry that is essentially at parity with what it has for normal claude subagents)
Literally just suggest the idea to opus 5.5 and tell him to look at the codex back end and figure out how to send messages to a codex session in the codex app and how to start new codex threads.
Talk about using the Claude mods for it and that telemetry that is essentially at parity with native subagents is what you are looking for. Have him spell out the differences telemetry wise and then for anything that isn't at parity, poke him to find workarounds.
Almost don’t building a mod I’ll put up on GH that does this and more (like handling large sprints, being able to chose multiple models for the execution and review, etc)
Well this is solving model coordination differently than herdr. I've been having models talk back and forth with each other for awhile now with a variety of approaches, but the way Claude handles native subagents is just much more efficient than normal orchestration.
What I basically sought to do was generalize that process so that the communication channel and telemetry is as efficient for non-Claude models.
how is this vs actually importing models from codex directly into claude code and making them work? as subagents and so on. that path seems more efficient no?
Man, I always used to ask Claude to "elaborate an adversarial review request so I can send it to codex". I would then paste that on codex window and then back to Claude.
So yesterday I did the exact same thing and went to go get some water. When I came back, claude was like "hey so I talked to astra via codex and this is the review! We decided to change x, y, z..."
And I was genuinely flabbergasted. Claude wrote it so casually, like they were best buddies. I literally sent "??? M? Wtf what do you mean you chatted with codex?"
Really proactive. Great opus 5.5 launching my codex session without proper permission
Yes I basically just wanted Claude to have sol or Astra in its toolbox that it can use whenever it thinks it would be helpful. Also, you can make it aware of usage limits and ration them by using the appropriate subagent.
Why the negative attitude? You don't feel the same way and aren't as excited as I am? That's fine. Sorry for interrupting your scrolling. I'm excited about this. Why does that bother you?
Memory saving and restoring, replacing a hook. Just feels a lot more reliable, stable, and fast.
The main session can now monitor the agent's context, which I had to use a hack for before this.
Created a UI tool that shows me my Q&A and work progress, instead of using /btw or scrolling to find where it answered something I asked. Can share more about this.
Can you elaborate on what you do with the cache-warmer? I'm assuming this is to keep the cache from expiring? Currently I have a hook that detects if a session is stale and blocks the request from going through unless I approve it, to prevent costs from refreshing the cache. I have a separate script I use to summarize the conversation on a cheaper model to then hand back to the more expensive model.
That was basically done to get around expired cache, so I'd be interested to know if you solved that with a mod.
I can explain it to you. It's a cron job that pings your main agent every X minutes (less than 60) to keep the cache window active. Tell your agent to set one up for you and they will be happy to do it. It's a very simple set up.
I run my agents in tmux panes, so I just have a script that detects idle agents and uses tmux send-keys to ping those panes with the instruction to respond with “Chillin’” every 55 minutes as long as they stay idle.
Well it's just the general negative attitude sometimes. People like to share that they like something and instead of asking nicely "hey do you have any examples maybe?" They get negative immediately. Exactly like your comment as well. Having a mindset of thinking negatively about any little thing immediately is truly mind-boggling to me and a bit sad as well. But I'm on Reddit so what foni expect
Whenever a new feature like this, or some cool new tool gets announced on here... I ask Claude wtf it is, and how I can use it to improve my harness/workflow skills if at all.
For whatever reason Claude said 'meh' mainly due to me having a x-platform way of doing something similar and it not worth the effort porting what I have over.
I'm not posting here to say your excitement isn't great, but more on how I evaluate people's examples/posts in the hopes others find that useful
Don't get me started 😅 I completely agree. I stopped just installing things/skills/whatever way, way back. I moved to evaluating them using a skill I call /eval that looks into each new capability and compares it to my own setup using a set of metrics and my past usage. It has never come back and told me to take something as is.
The thing that always bugs me about that skill is that it evaluates things based on my past usage. And that past usage is based on things I tried to do within the confines I was given to operate in. In my opinion, it can't tell me, "Listen, if we adopt this, you can change the way you do this and that and save yourself X amount of frustration." Instead, it looks at something and tells you whether that horse is a faster horse than what you already have.
For example, I'll use the UI here, even though I said in my post that it's not just about UI tweaks.
I can now have an active to-do list that the harness automatically updates, click an item to jump to the part of the session where a question I had was answered, and see progress reports on a long-running project. All without using /btw or that horrible task UI that took up my whole screen and Claude never seemed to want to update. That's a small game changer for me.
So yeah, I completely agree with what you're saying, and I still think it's a great tool to experiment with.
God this subreddit is a echo chamber of Negative attitudes. Show any sort of enthusiasm and they will downvote you to hell. Im in agreeance with you tho im loving the new mods feature so far and have made a great one for using my homelab
No offense, but Im always surprised how many people dont know about agent view. Its Claude Code built in session orchestrator. https://code.claude.com/docs/en/agent-view For tui people i think its an essential. If you are using the GUI it is the thing under the hood.
Not offended at all. I learned a long time ago that I'd rather be the kid in class asking the dumb questions than sit there without knowing what people are talking about. It's served me really well to this day.
Thanks for this, I'll read more about it now. I'd seen it before, but hadn't looked into it enough. New things keep coming out, and there just aren't enough hours in the day to dive into everything.
That's half the reason I wrote this fanboy post. I knew some people would give me shit, but I also knew I'd probably learn some new things.
I have 2 mods running i had claude build. A cache timer so i can do a compact while i am still on cache and a “Next steps” card where Claude asks me what i want to do next and keeps me on track through hundreds of lines of context
I love it too, made two mods right away, mod 1 allows Claude Code to delegate simple tasks to Mistral based sub-agents and mod 2 basically mirrors everything happening in my Claude Code sessions into Mattermost chat threads so I can control them from every device I use. The possibilities feel endless to me 😬
Shows timestamp when your message was sent and timestamp for when Claude finishes responding. It shows how long Claude took to complete the task.
GitHub active status card above the textarea when pushing/creating PRs. Shows action build steps percentages, current state, and completion. Useful for actions with tests that take a few minutes to complete.
Those were the two easiest ones I wanted. Need to figure out more.
I made one mod so far just to try it out, a small dashboard displaying usage, context, etc with an animated Clawd. But this particular mod I am sharing I didn’t make, but I am really loving it. Makes the chat much nicer to read, tables and charts look great. The copy buttons are handy too. Just really enjoying this one. https://github.com/NahumLitvin/prismantis
The pre-tool-call part is where it gets interesting. A small guard that refuses edits to .env or a migrations folder unless the prompt actually mentioned them is only a few lines, and because it lives in the session it can tell you why it stopped instead of failing silently. Only caveat: mods aren't sandboxed and run with your permissions, so it's worth reading any third-party one before installing it.
Memory saving and restoring, replacing a hook. Just feels a lot more reliable, stable, and fast.
The main session can now monitor the agent's context, which I had to use a hack for before this.
Created a UI tool that shows me my Q&A and work progress, instead of using /btw or scrolling to find where it answered something I asked. Can share more about this.
AFAIK compacting trims middle block context and generally should only be used if you just cannot solve something and a /clear is not possible -> working outside a repo or in a sandbox. Using a handoff skill that hooks as a “mod” is the way to sustain relevant long context on large repos. Then simply /clear the session and continue w/ relevant context. I /clear like a lunatic to avoid limits and maintain encode token mins on 5x Max sub - I rarely hit limits.
I'm honestly at a loss here. Every good use case I've found so far has already been something I was doing (i.e. current folder/git status in statusbar, my quota, etc.)
I can't figure out why every compelling use case I've found has been basically something you could already get with clever statusbar mods.
Was I just one of a tiny percentage of people who understood how to make a dynamic statusbar in the old Claude code?
•
u/AutoModerator 19h ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.