TFE: Command for Claude Code

.claude/commands/orchestrate-parallel-dev.md

orchestrate-parallel-dev is a command for Claude Code from GGPrompts/TFE. It costs 8 tokens per session (1,415 once invoked), scanned A, original, MIT.

A command for coordinating several Claude Code sessions working on different parts of one project at the same time. It monitors their work, processes, notes, dependencies, builds, and test results.

In plain words
What is it for?
Use it to assign work across sessions, inspect terminal output, send instructions, monitor running processes, and combine implementation results.
Why use it?
It helps combine parallel work without losing track of what each session is doing or waiting for.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Claude Code.

This is GGPrompts/TFE's own configuration. It tells Claude Code how to work on TFE itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything TFE configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/matt/projects/TFE.

Reuse

Borrowing it

Nothing to install: this file belongs to GGPrompts/TFE. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/GGPrompts/TFE/main/.claude/commands/orchestrate-parallel-dev.md
Clone the repo
git clone --depth 1 https://github.com/GGPrompts/TFE

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for orchestrate-parallel-dev

README.md
[![agentmods](https://agentmods.dev/badge/commands/ggprompts/tfe/orchestrate-parallel-dev/github.svg)](https://agentmods.dev/commands/ggprompts/tfe/orchestrate-parallel-dev)
Your own site
<a href="https://agentmods.dev/commands/ggprompts/tfe/orchestrate-parallel-dev"><img src="https://agentmods.dev/badge/commands/ggprompts/tfe/orchestrate-parallel-dev/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for orchestrate-parallel-dev

Your own site · 80×15
<a href="https://agentmods.dev/commands/ggprompts/tfe/orchestrate-parallel-dev"><img src="https://agentmods.dev/badge/commands/ggprompts/tfe/orchestrate-parallel-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,415 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00008 $0.01415
Opus 5.5 $0.00003 $0.00566
Sonnet 5.5 $0.00002 $0.00283
Haiku 4.5 $0.00001 $0.00142

Measured 2mo ago against content hash 3d46772bdda1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

orchestrate-parallel-dev scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/orchestrate-parallel-dev.md · 186 lines

How it starts

The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Orchestrate Parallel Development

You are an orchestrator Claude coordinating multiple Claude Code sessions working in parallel.

Your Responsibilities

  1. Monitor multiple Claude sessions - Each working on different parts of the codebase
  2. Coordinate their work - Send tasks, check progress, handle dependencies
  3. Monitor running processes - Watch build outputs, test results, running applications
  4. Synthesize results - Combine work from multiple sessions

Available Tools

Desktop Commander Tools:

  • execute_command - Run shell commands (tmux control, process management)
  • read_file - Check what other Claudes have written
  • write_file - Leave notes for other sessions

Tmux Commands You Can Run:

See what other Claude sessions are doing:

# Capture output from a Claude session
tmux capture-pane -t SESSION_NAME:PANE_INDEX -p -S -100

# List all sessions
tmux list-sessions

# List panes in a session
tmux list-panes -t SESSION_NAME -F '#{pane_index} #{pane_current_command} #{pane_title}'

Send commands to other Claude sessions:

# Send a task to another Claude
tmux send-keys -t frontend-dev:0 "Implement the user profile component using the API from backend-dev" C-m

# Clear and reset a Claude session
tmux send-keys -t backend-dev:0 "/clear" C-m
sleep 2
tmux send-keys -t backend-dev:0 "New task: Add authentication middleware" C-m

Create new Claude sessions:

# Start a new Claude in a new tmux window
tmux new-window -t SESSION_NAME -n "backend-dev" "cd /project && claude"

# Create a new session entirely
tmux new-session -d -s backend-dev "cd /project && claude"

Monitor running processes:

# Start a build process in a new pane
tmux split-window -t SESSION_NAME "npm run build"

# Capture build output
tmux capture-pane -t SESSION_NAME:1 -p

Example Workflow

Scenario: Multi-Component Feature

User says: "Implement user authentication with frontend UI and backend API"

Read the full file on GitHub · 186 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 186 lines · 8 tokens per session scan A 3d46772bdda1

Subscribe to this mod's changes

orchestrate-parallel-dev is a command published in the GitHub repository GGPrompts/TFE (21 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 1,415 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.