flows

ntkode/notkode-mods

A file browser pane inside Claude Code: walk the project, read Markdown rendered, code highlighted, and pictures drawn in the terminal; see the files Claude touched this session.

letusnotc/folder-map

Side panel that opens when Claude edits files: the whole folder tree, every edited file numbered in order, and a highlighted trail from the project root to the file being edited. /folder-map toggles it.

jessewaites/claude-mods

A file tree and text editor in a pane: /editor, say "open the editor", or ask Claude to open a file in it

mmedum/glimt

A quiet side pane: what this session is doing now, its plan, its agents as a tree, and every other Claude Code session with theirs

curran-gehring/claude-dot

An always-on companion for Claude Code, after OpenAI's dots: a named avatar that keeps standing responsibilities, runs them on schedules in the background, does read-only proactive research, keeps notes you can read, and gates risky actions with Custom Rules and an independent Auto-review.

mephistopheles4/grimoire

A spellbook of agent skills for AI. Cast wisely. Four skills: eagle-eye, which lays coupled decisions out as a morphological box and renders one self-contained page that reads any configuration back; groundtrack, which turns a plan or a written change into a call graph with recorded traces through it, on a page a reader can step; contract, which interviews a person to agree the terms for a skill, an agent or a CLAUDE.md of their own, then generates its file from that contract and validates it; and head-chef, which makes a Claude Desktop session the lead of the sessions it starts, with their model and effort set, their milestone reports, relays between them, and cleanup when the owner says a session is done. And one pane for Claude Code: Brigade, opened with /brigade or when the head-chef skill loads, which shows the sessions a lead session started as compact rows, each with its phase, live busy or idle state, age, cache warmth, latest report and pull request, behind a switch between a Sessions view, a Pull requests view and a Decisions view, which lays out the decisions a lead logs as a review queue for the owner to read, with the lead's hand-off folded at its foot, with a coloured pill for each pull request and the lead session's own rate limits and context. The pull request details need the GitHub command line tool, gh, installed, signed in, and run in a GitHub repository.