cost-ticker

Cockpit

English · Português · Español

An instrument panel for Claude Code. 309 mods for the terminal: 52 panels that stay in sight and switch on and off in /cockpit, plus guards, prompt automations, instant commands and focus helpers. Every mod is a small plugin you install with one line.

/plugin marketplace add MatheusChiodi/cockpit
/plugin install git-band@cockpit
/cockpit

Mods are TypeScript functions that run inside Claude Code and change how it behaves: they intercept tool calls, rewrite prompts, draw panes and bands, and register slash commands. They need Claude Code 2.1.287 or newer (built against 2.1.296).

Install

From GitHub, inside Claude Code:

/plugin marketplace add MatheusChiodi/cockpit
/plugin install <mod>@cockpit

From a local folder:

git clone https://github.com/MatheusChiodi/cockpit
claude plugin marketplace add ./cockpit
claude plugin install git-guard@cockpit

Just to try one, without installing:

claude --plugin-dir ./cockpit/mods/turn-timer

Remove a mod with /plugin uninstall <mod>@cockpit. Turn every mod off at once with claude --safe-mode.

Panels and settings

The 52 mods under Always visible are panels: bands above the prompt or status line entries that update on their own (git, context, cost, tests, CI, tasks, deadline, weather). None needs a command to show up.

The cockpit mod is their settings pane, and it comes along as a dependency of any panel.

Both choices are kept between sessions. A band disappears or returns at once; a status line entry disappears at once and returns on its next update. A panel switched off stays installed and simply does not draw.

Bands stack in the order the mods load, and the status line holds one entry per mod. With many panels on, the terminal gets crowded: start with four or five and adjust in /cockpit.

Language

Every mod speaks English by default and can switch to Brazilian Portuguese or Spanish. The language is set once, in /cockpit, and every installed mod follows it: band labels, status line words, command output, guard messages, toasts and notifications. Without the cockpit mod installed, mods stay in English.

Slash command descriptions in the typeahead are read when a session starts, so they follow a language change on the next session. To make Claude itself answer in the chosen language, install reply-language.

Catalog

Visual language

Every panel is drawn the same way, so several of them read as one instrument:

• Instrument row: a colored rail, a fixed-width label, then values. Stacked, the bands line up in columns.
• One hue per subject on the rail: Git, Session, Project and Daily. Green, amber and red are reserved for the state of a value.
• Thin-line gauges (━━━━───) instead of block bars.
• A short, lowercase status line: label state detail, as in tests ✓ 14:32 · 3.1s.
• Colors come from your Claude Code theme. The drawing lives in kit/kit.tsx, copied into each mod at build time.

Suggested sets

Before you install

• Mods are not sandboxed. They run with the same reach as Claude Code. Read a mod's hooks/register.ts before installing it; every one here is short.
• Guards are a seat belt, not a vault. They match known shapes of commands and paths: an obfuscated command can get through, and a legitimate path can be refused. Keep Claude Code's own permissions configured.
• Some guards ask instead of blocking. prod-guard, install-ask and the others that say so force the confirmation prompt even when the command was already allowed.
• A few mods call a model and cost tokens; their description says so.
• Some panels use the network and stay hidden when there is no answer: dolar-status (AwesomeAPI), weather-status (wttr.in, located by IP), api-status (Anthropic's status page), ports-band (localhost only).
• ci-status and pr-status need an authenticated gh.
• Git panels poll the repository every 30 to 60 seconds.
• No sound. In this version $.audio.play only plays on macOS, so notifications use the native channel.
• The mods API is early access and may change between Claude Code releases.

Development

npm install
npm run build              # manifests, the hub's panel list, previews and the three READMEs
npm run check              # tsc + claude plugin validate on every mod + claude plugin test where tests exist
node scripts/mod.mjs <mod> # the same loop for one mod, without touching shared files

mods.json is the single source: name, category, descriptions in three languages and the preview lines of every mod.

mods/<name>/
  hooks/register.ts(x)   the mod
  hooks/strings.ts       every user-facing text, in en, pt and es
  types/index.d.ts       the $.state contract, for mods that draw
  tests/                 run by `claude plugin test`

plugin.json, hooks.json and each mod's copy of the kit are generated.

Adding mods with the agent. The repository ships a Claude Code agent, cockpit-mod-builder (.claude/agents/), that knows the conventions: the language pattern, the visual kit, the engine rules that trip people up, and the one-mod loop. Open Claude Code in the repository and ask for it by name, giving a category and the mods you want.

The type check uses the API declarations Claude Code itself writes. They are not in the repository: run a mod with claude --plugin-dir mods/<name> and copy mods/<name>/.claude-plugin/types/claude-code/index.d.ts plus claude-code-tools/index.d.ts into engine-types/.

The mods ecosystem

Surveyed on 2026-10-13 through gh api and the official documentation. Star counts are from that day.

• Announcement: claude.com/blog/claude-code-mods
• Documentation: code.claude.com/docs/en/plugins/mods/overview
• Built-in mods: anthropics/claude-code/mods
• Official samples: anthropics/claude-code-playground

Other ways people customize Claude Code, which are not mods: claude-hud and ccstatusline (status line scripts), ccusage (a CLI over the transcripts), tweakcc (patches the install), cc-safety-net (a PreToolUse hook).

License

MIT