SLOPSHOPPER

ram

Belegter Arbeitsspeicher (macOS) als Eintrag in der Leiste über dem Eingabefeld

newbandprocesstimer
v0.1.0MITupdated 2026-10-14allorders1studio/claude-code-mods/ram
A shopper browsing a rack in a slop shop
README

claude-code-mods

Four Claude Code mods (plugins that change the interface itself): a deploy status bar, a tasks pane, a RAM indicator and a Git worktree overview. The three that draw above the input field share one bar.

The UI texts of all mods are in German.

ModWhat it showsWorks for you if
worktreesAll Git worktrees with open workyou use Git (nothing else needed)
dokploy-statusbarLast Dokploy deploy per appyou deploy with Dokploy and have the private dokploy CLI
todosOpen tasks of the current repo from a G-Brainyou have an MCP server claude.ai G-Brain with get_page
ramUsed memory in the baryou use macOS

Installation

claude plugin marketplace add allorders1studio/claude-code-mods
claude plugin install worktrees@claude-code-mods

Replace worktrees with dokploy-statusbar, todos or ram as needed, then run /reload-plugins inside Claude Code.

worktrees

The only mod that needs nothing but Git. /worktrees lists every worktree of the current repo and tells you which ones can be deleted.

╭──────────────────────────────────────────────────────────╮
│ feature-search  feat/search                              │
│ 3 Dateien uncommittet  ·  letzter Commit heute           │
│ Pfad kopieren                                            │
╰──────────────────────────────────────────────────────────╯
╭──────────────────────────────────────────────────────────╮
│ fix-login  fix/login                                     │
│ 2 Commits nicht in main, nicht gepusht  ·  letzter Commit gestern │
╰──────────────────────────────────────────────────────────╯
╭──────────────────────────────────────────────────────────╮
│ old-experiment  exp/cache                                │
│ nichts offen – kann weg  ·  letzter Commit vor 12 Tagen  │
╰──────────────────────────────────────────────────────────╯
Neu laden  3 Worktrees · 2 mit offener Arbeit · Stand 23:20:56

Status line while worktrees hold open work:

2 von 3 Worktrees mit offener Arbeit · /worktrees
  • Uncommitted files per worktree
  • Commits not in main (compared against origin/<default branch>)
  • Pushed or not pushed
  • "kann weg" (can go) for worktrees with nothing left to lose; "Stand unklar" when the comparison with main fails
  • Card colors: red uncommitted, yellow not pushed, cyan pushed, green can go

Command: /worktrees. Requirements: Git.

dokploy-statusbar

A bar above the input field with the last Dokploy deploy of every app belonging to the current repo.

 ● api-app  ● web-app  ● worker running 1:20  ● docs ausstehend          23:20
 > _
  • Dot: green (done), red (error), yellow (running), grey (pending), magenta (unknown)
  • App name links to its Dokploy page; on error it links to the deployments tab
  • Button "Log" on error: writes the last 80 build-log lines into the input field
  • "ausstehend" (pending): a commit since the deployed one touched the service's watch paths
  • running m:ss while a build is in progress
  • After git push, polls every 5 s for 2 minutes instead of every 30 s
  • Toast when a deploy finishes; the last fetch time is shown faintly at the far right of the shared bar (see below)

Command: /deploys (refresh now).

Requirements, honestly:

  • The dokploy CLI from allorders1studio/dokploy-cli. That repository is currently private; it is not the npm package of the same name.
  • macOS with Homebrew paths: /opt/homebrew/bin/dokploy, /opt/homebrew/lib/node_modules/dokploy-cli and /opt/homebrew/bin/node are hard-coded in hooks/register.tsx and hooks/discover.cjs.

How it works

hooks/discover.cjs asks Dokploy (through the CLI's API module) for all services and keeps those whose Git source matches git remote get-url origin. It also reads each service's watchPaths. No configuration per repo is needed. API keys stay inside the CLI; the mod never sees them.

todos

/tickets opens a pane "Aufgaben" with the open tasks of the current repo, read from a G-Brain (GBrain) knowledge store through its MCP server. The bar above the input field shows Aufgaben N (parked tasks not counted): red if one is overdue, yellow if one is due today or has high priority. A click on it opens the pane.

╭──────────────────────────────────────────────────────────╮
│ Abo-Bestellungen per Tag kennzeichnen                    │
│ überfällig · gestern                                     │
╰──────────────────────────────────────────────────────────╯
╭──────────────────────────────────────────────────────────╮
│ HubSpot-Workflow für die Ankündigungsmail                │
│ seit 2026-10-14  ·  Prio hoch                            │
╰──────────────────────────────────────────────────────────╯
Neu laden  2 offen · Stand 23:20:56

Order: tasks with a due date first (by date), then high priority, then the rest in page order, parked tasks last and dimmed. A click on a task writes it, with its detail lines, into the input field; "Details ›" opens the detail view.

How it works: the mod reads the page todo, takes the list slugs from the lines - [[todo/<name>]] — … under ## Projekte, reads each list and keeps those whose Repos: line names the repo of git remote get-url origin. A repo may be on several lists; each is shown as its own section. Loaded at session start, every 5 minutes, on /tickets and on "Neu laden".

# To-do — My project

Repos: `owner/repo`, `owner/other-repo`

## Offen
- [ ] Task title · seit 2026-10-14 · fällig 2026-10-16 · Prio hoch
  - any number of detail lines
- [ ] Waiting task · wartet auf the supplier
- [ ] Parked task · geparkt

## Erledigt
- [x] …

Parts after · in the title line are read as seit, fällig (both YYYY-MM-DD), wartet auf …, Prio hoch and geparkt; anything else stays in the text. [[a/b]] is shown as a/b.

Requirements, honestly: an MCP server whose tools include get_page, put_page and remember (the mod finds it by these tools, since its name differs between terminal and desktop app); get_page takes { slug, content_only } and answers with JSON containing compiled_truth. In auto mode a mod's MCP call is refused unless get_page is allowed in permissions.allow, e.g. "mcp__<server>__get_page". Without such a store this mod is of no use to you. No credentials are configured here; the connection is the session's own.

Command: /tickets.

ram

Used memory in the bar, polled every 10 seconds from memory_pressure -Q (macOS only): RAM 66% is 100 minus the "free percentage". Grey below 80 %, yellow from 80 %, red from 90 %. Where the command is missing or fails, the entry is left out without a message.

The shared bar

dokploy-statusbar, todos and ram draw into the same band above the input field, which only one hook can fill. Each mod reads the tree of the hooks inside it (next(e)), adds its entry under a sorted key and rebuilds the bar, so the layout does not depend on plugin order. Apps on the left, the rest on the right, separated by · , the Dokploy fetch time last:

 ● api-app  ● web-app  ● worker running 1:20            Aufgaben 3 · RAM 66% · 23:20
 > _

Without Dokploy only Aufgaben and RAM appear. hooks/bar.tsx is the same file in all three mods.

Structure

.claude-plugin/marketplace.json   marketplace "claude-code-mods"
<plugin>/
  .claude-plugin/plugin.json      manifest (name, version)
  hooks/register.tsx              the mod: panes, bands, commands, atoms
  hooks/*.ts                      pure logic (parsing, scanning) plus tests
  types/index.d.ts                state types per plugin

Mods use the claude-code mod API. Tests of the pure logic sit next to the code (*.test.ts); UI behavior can be tested with claude-code/testing.

License

MIT, see LICENSE.

Source 4 files
hooks/register.tsx 34 lines
1import { atom, read, update } from 'claude-code'
2import type { EngineInterface, Register } from 'claude-code'
3
4import { addToBar } from './bar'
5import { parsePressure, ramColor } from './parse'
6
7const used = atom({ plugin: 'ram', key: 'used' } as const, null)
8
9// Fehler (kein macOS, Befehl fehlt) lassen den Eintrag verschwinden, ohne Toast: die Leiste soll nie nerven.
10async function poll($: EngineInterface) {
11  try {
12    const r = await $.process.run(['/usr/bin/memory_pressure', '-Q'], { timeoutMs: 5000 })
13    await update($, used, () => (r.exitCode === 0 ? parsePressure(r.stdout) : null))
14  } catch {
15    await update($, used, () => null)
16  }
17}
18
19export const register: Register = on => {
20  on('session.start', async ($, e, next) => {
21    void poll($)
22    $.clock.every(10000, () => void poll($))
23    return next(e)
24  })
25
26  on('ui.render', { component: 'AbovePrompt' }, async ($, e, next) => {
27    const inner = await next(e)
28    const pct = await read($, used)
29    if (e.props.hasSurvey || pct === null) return inner
30    const { Text } = $.ui.resolve(e)
31    return addToBar($.ui.resolve(e), inner, 'right', '2-ram', <Text color={ramColor(pct)}>RAM {pct}%</Text>)
32  })
33}
34
hooks/bar.tsx 35 lines
1import type { EngineInterface, RenderElement } from 'claude-code'
2
3type Tree = { props?: { key?: string }; children?: Tree[] }
4type UI = ReturnType<EngineInterface['ui']['resolve']>
5
6// Gemeinsame Leiste über dem Eingabefeld, byte-gleich in dokploy-statusbar, todos und ram (Plugins sind getrennt).
7// `AbovePrompt` ist eine Instanz, die Hooks nesten (erster = äußerster) und deren `next(e)` den Baum der inneren liefert.
8// Jeder Mod liest daher den Baum der inneren, hängt seinen Eintrag unter einem Schlüssel ein und baut die Leiste neu;
9// links/rechts und Reihenfolge ergeben sich aus dem Schlüssel (Sortierung), nicht aus der Plugin-Reihenfolge.
10// shortcut: erkennt nur Bäume mit `key="bar"`; fremde Inhalte stehen darüber, bei Bedarf gezielter einordnen.
11export function addToBar(ui: UI, inner: RenderElement, side: 'left' | 'right', key: string, node: RenderElement): RenderElement {
12  const { Box, Text } = ui
13  const tree = (inner ?? {}) as Tree // falls `next(e)` doch nichts liefert
14  const isBar = tree.props?.key === 'bar'
15  const part = (k: string) => (isBar ? (tree.children?.find(c => c.props?.key === k)?.children ?? []) : [])
16  const entry = (<Box key={`bar:${key}`}>{node}</Box>) as Tree
17  const place = (k: string, items: Tree[]) =>
18    [...items.filter(c => c.props?.key !== `bar:${key}` && c.props?.key !== 'bar:sep'), ...(side === k ? [entry] : [])].sort((a, b) =>
19      String(a.props?.key).localeCompare(String(b.props?.key)),
20    ) as RenderElement[]
21  const left = place('left', part('bar:left'))
22  const right = place('right', part('bar:right'))
23  const bar = (
24    <Box key="bar" justifyContent="space-between">
25      <Box key="bar:left" gap={1}>
26        {left}
27      </Box>
28      <Box key="bar:right">
29        {right.flatMap((c, i) => (i ? [<Box key="bar:sep"><Text color="subtle"> · </Text></Box>, c] : [c]))}
30      </Box>
31    </Box>
32  )
33  return !isBar && (tree.children?.length ?? 0) > 0 ? <Box flexDirection="column">{inner}{bar}</Box> : bar
34}
35
hooks/parse.ts 8 lines
1// Letzte Zeile von `memory_pressure -Q`: „System-wide memory free percentage: 34%“. Belegt = 100 − frei.
2export const parsePressure = (out: string): number | null => {
3  const m = out.match(/memory free percentage:\s*(\d{1,3})%/)
4  return m && Number(m[1]) <= 100 ? 100 - Number(m[1]) : null
5}
6
7export const ramColor = (pct: number) => (pct >= 90 ? 'error' : pct >= 80 ? 'warning' : 'subtle')
8
types/index.d.ts 6 lines
1declare module 'claude-code' {
2  interface PluginState {
3    ram: { used: number | null }
4  }
5}
6