Claude Code mod
crew
A resident product team in Claude Code, run from its own pane with buttons and fields, no command needed: a PM splits your PRD into features and acceptance criteria, QA writes a test case for each, a UI/UX designer writes a design for each feature that you approve on one page with the PRD draft and the roles' questions, a tech lead breaks the criteria into tasks and reviews the code, a full-stack agent builds the tasks on crew's own git branch and worktree, and crew runs your test command and maps the results to the test cases. Each role runs on Claude or Codex, from a floor you set, stepping up with how hard the work is. Gaps and product questions come back to you in the pane. A heartbeat looks after the work every five minutes, a restart asks before going on, and token reminders go to Claude, which acts on usage only as you allow. The board is held to the PRD as it stands. Memory lives in the repo. Work in progress.
Install
/plugin marketplace add PeterTing/claude-mod
/plugin install crew@claude-modMods install like plugins. Run /reload-plugins or start a new session to load it.
What it can access
- Reach
- Unknown
- Sees
- subagent spawns, every tool call, mcp__crew__board_read calls, mcp__crew__board_write calls, mcp__crew__thread_post calls, mcp__crew__review_submit calls, mcp__crew__thread_read calls, mcp__crew__ask_person calls, mcp__crew__crew calls, mcp__crew__memory_save calls, mcp__crew__memory_search calls, every prompt, compaction
- Draws in
PaneAbovePrompt- Hooks
session.startagent.offeragent.spawncommand.runtool.callsession.receiveprompt.submitsession.compactturn.startturn.stepturn.completeui.pressui.inputui.selectui.renderprompt.compose
From a static scan of the mod's code by awesome-claude-code-mods. It shows what the code asks for, not a security review.
How Claude Code mods work
- A mod is a plugin with a JavaScript or TypeScript module that runs inside Claude Code (version 2.1.287 or later). It can draw panes beside the transcript, a band above the prompt, buttons and toasts, restyle the spinner and tool rows, and watch or rewrite tool calls and prompts.
- It installs like any plugin: add its marketplace with /plugin marketplace add owner/repo, then /plugin install name@marketplace.
- Check what a mod can reach before installing: it runs with your permissions. Reach goes from drawing only, to reading files, to writing files or running processes, to the network. Run claude plugin validate on a clone to list its hooks and calls without running it.
- Turn one off from the Installed tab in /plugin, or start Claude Code with --safe-mode to skip every customization for a session.
Details
- Repository
- PeterTing/claude-mod
- Folder
mods/crew- Marketplace
claude-mod- Author
- PeterTing
- License
- MIT
- Last updated
- 31 October 2026
- Listed in
- awesome-claude-code-mods
FAQ
What is crew?
A resident product team in Claude Code, run from its own pane with buttons and fields, no command needed: a PM splits your PRD into features and acceptance criteria, QA writes a test case for each, a UI/UX designer writes a design for each feature that you approve on one page with the PRD draft and the roles' questions, a tech lead breaks the criteria into tasks and reviews the code, a full-stack agent builds the tasks on crew's own git branch and worktree, and crew runs your test command and maps the results to the test cases. Each role runs on Claude or Codex, from a floor you set, stepping up with how hard the work is. Gaps and product questions come back to you in the pane. A heartbeat looks after the work every five minutes, a restart asks before going on, and token reminders go to Claude, which acts on usage only as you allow. The board is held to the PRD as it stands. Memory lives in the repo. Work in progress. It is a mod for Claude Code, from PeterTing/claude-mod on GitHub.
What can the crew mod access?
Its reach could not be worked out from its code. It sees subagent spawns, every tool call, mcp__crew__board_read calls, mcp__crew__board_write calls, mcp__crew__thread_post calls, mcp__crew__review_submit calls, mcp__crew__thread_read calls, mcp__crew__ask_person calls, mcp__crew__crew calls, mcp__crew__memory_save calls, mcp__crew__memory_search calls, every prompt, compaction. It draws in Pane, AbovePrompt. Like any mod, it runs with your permissions.
How do I install crew?
Inside Claude Code (v2.1.287 or later), run /plugin marketplace add PeterTing/claude-mod and then /plugin install crew@claude-mod.
More pane & dashboard mods
crew
Fahim-2135/crew
An always-on team of AI agents on your own computer: chat with them in the Crew window, and they work with your files, the web, your apps and the screen. Anything that can't be undone asks you first.
crew
sstani-bgv/claude-crew
Agents panel with pixel crabs and a progress strip above the prompt, for any subagents. Based on savvy-progress by johnnyvizz (MIT).
crew
Ascurse/claude-mods
Crew: predicts the next step after each answer and suggests the 5 session agents that fit it, drafts a task prompt with Haiku and starts the agent in the background, from its own pane
crew-hq
aayanrehman/crew-hq
Crew HQ: an HQ pane over every project's TASKS.md and a team of five subagents that pick up @claude tasks, huddle, and report back
crab-agents
ecombuilder-web/TripleDigit-crab-agents
Right-side Agents pane by Triple Digit (triple-digit.com, tailored AI solutions for each company): every working and recently finished session as a hat-wearing crab, with model, effort, context, progress, needs-you highlights and usage limit countdowns.
critters
ErnestTramp/claude-critters
Pixel critters above the prompt for each background agent, a different sprite per model (Opus, Sonnet, Haiku, Fable). Expand for a task list, click one for its transcript, or hide them in the footer.
Browse the most popular Claude Code mods, all pane & dashboard mods, or the skills and MCP server directories.