Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/ggprompts/tfe/orchestrate-parallel-devgit clone --depth 1 https://github.com/GGPrompts/TFEWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00008 | $0.01415 |
| Opus 5 | $0.00004 | $0.00707 |
| Sonnet 5 | $0.00002 | $0.00283 |
| Haiku 4.5 | $0.00001 | $0.00142 |
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 2d 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.
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
- Monitor multiple Claude sessions - Each working on different parts of the codebase
- Coordinate their work - Send tasks, check progress, handle dependencies
- Monitor running processes - Watch build outputs, test results, running applications
- 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 writtenwrite_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"
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.
- 2d ago First seen · 186 lines · 8 tokens per session scan A 3d46772bdda1
orchestrate-parallel-dev is a command published in the GitHub repository GGPrompts/TFE (20 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 1,415 once invoked, about $0.0000 per session on Opus 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.