SkillFoxx

claude-mods plugin

Two plugins change how Claude Code output looks: replies in the glamour dark style and tool calls as compact one-liners.

  • 83 ★ on the repository
  • Last commit
Plugin

Extended access

Why this level

  • The mods run TypeScript code through hooks in your session and change how replies and tool results are displayed.
  • The `tool-lines` mod hides the call result block, so errors are easy to miss.
All reasons and checks

tickloop/claude-modsAuthor:Tickloop

Install

Works in

Manual install

claude plugin marketplace add Tickloop/claude-mods

Then `claude plugin install glamour-dark@claude-mods` and `claude plugin install tool-lines@claude-mods`, then `/reload-plugins`.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The mods run TypeScript code through hooks in your session and change how replies and tool results are displayed.
  • The `tool-lines` mod hides the call result block, so errors are easy to miss.

This is third-party code. Review the repository files before installing.

What it does

claude-mods is a marketplace of two mods that make Claude Code output easier to read. The `glamour-dark` mod draws the model text replies in the default glamour dark style. The `tool-lines` mod shows each tool call as one line of the form `tool_call: Tool(input) - meta` and hides the result block. The mods load as plugins through a hooks module and install separately. For development you clone the repository and start Claude Code with `--plugin-dir` flags to load the mods for one session.

Who it is for. People who spend long sessions in Claude Code and are tired of long tool output blocks and walls of reply text.

Good fit when

  • A model reply with code and lists reads poorly in a terminal and you want one dark styling.
  • The session is long and tool result blocks hide the course of the work.
  • You want a quick scan of which tools the agent called and with what input.
  • A Claude Code modding developer looks at an example of hook-based plugins.

Not a fit when

  • You need tool results in view: `tool-lines` hides the result block and errors are easy to miss.
  • A terminal with a light theme: `glamour-dark` targets the dark style only.
  • A shared environment with strict policies: hooks run TypeScript code inside the session.

Example request

Install the glamour-dark mod and run a long reply with a table and a code block so I can judge the styling.

Limitations

The mods redraw what you see. The `tool-lines` mod hides the call result block, so a tool failure may go unnoticed; disable it while debugging. The TypeScript code of the mods runs through hooks in your session, so read it before installing. The repository has no license file, and style settings are not documented. Pick up a new mod version with `claude plugin marketplace update claude-mods` and `/reload-plugins`.

How to disable. Uninstall a mod with `claude plugin uninstall glamour-dark@claude-mods` or `claude plugin uninstall tool-lines@claude-mods`, then run `/reload-plugins`. Remove the source from your marketplace list.

FAQ

How do I install the mods?

Run `claude plugin marketplace add Tickloop/claude-mods`, then `claude plugin install` for each mod. The same works inside a session through `/plugin marketplace add`.

How do glamour-dark and tool-lines differ?

`glamour-dark` restyles the model text replies. `tool-lines` folds each tool call into one line and hides the result block.

How do I apply a new mod version?

When `version` in `plugin.json` changes, run `claude plugin marketplace update claude-mods` and `claude plugin update`. Then `/reload-plugins` in open sessions.

Can I try a mod without installing?

Yes: clone the repository and run `claude --plugin-dir ./glamour-dark --plugin-dir ./tool-lines`. The mods load for that session only.

How do I make the mods permanent when running from a clone?

Add an alias for `claude` with `--plugin-dir` flags pointing at the mod folders in `~/.zshrc` or `~/.bashrc`. An example is in the Development section.

Discussion

No questions or reviews yet.

Plugins

A marketplace of 70 small Claude Code plugins with panes: notes, a task board, a context meter, utilities and a Git change viewer

PluginMinimal access120

A marketplace of 17 Claude Code mods: token-spend breakdown, a rollback edit timeline, assumption tracking, a verification board and a live command feed

PluginExtended access873

Four Claude Code mods: cache cost, screen-recording masking, a /goal meter and a guard against edit conflicts

PluginExtended access137
Needs a VPN

A Claude Code plugin that catches your corrections in chat and, after review, writes them into CLAUDE.md and AGENTS.md

PluginExtended access1.9K

A Claude Code panel for several projects: statuses, button decisions, Git, PR, CI and usage limits in one window.

PluginExtended access79

A marketplace of fourteen plugins for Claude Code power users: model council, email, calendar, video digests and routine tasks

PluginBroad access831

README in short

The README is a few paragraphs: a table of mods, marketplace installation, version updates and a development mode with the `--plugin-dir` flag.

README badge

Report a problem