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.
git clone --depth 1 https://github.com/TheLobbi/claudeWrote 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.
[](https://agentmods.dev/commands/thelobbi/claude/improve-orchestration)<a href="https://agentmods.dev/commands/thelobbi/claude/improve-orchestration"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/improve-orchestration.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00554 |
| Opus 5 | $0.00000 | $0.00277 |
| Sonnet 5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
improve-orchestration 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 7d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/improve-orchestration
Quick Usage: /improve-orchestration [target] --mode=analyze --depth=deep
Optimize orchestration patterns across Claude Code agents, production systems, GitHub workflows, and multi-system coordination.
Core Parameters
| Parameter | Type | Purpose | Example |
|---|---|---|---|
| target | string | What to optimize | claude-code, production, github, all |
| --mode | select | Analysis mode | analyze, optimize, implement |
| --depth | select | Analysis depth | shallow, deep, exhaustive |
| --focus | list | Specific areas | latency,conflicts,patterns |
Quick Examples
```bash
Analyze Claude Code orchestration
/improve-orchestration claude-code --mode=analyze
Full optimization of all systems
/improve-orchestration all --mode=optimize --depth=exhaustive
Fix specific issues
/improve-orchestration production --focus=conflicts,latency ```
What It Does
8-Phase Orchestration Improvement:
| Phase | Focus | Duration |
|---|---|---|
| 1. Discovery | Find orchestration points | 0-15 min |
| 2. Analysis | Identify patterns & anti-patterns | 15-35 min |
| 3. Design | Create improved architecture | 35-55 min |
| 4. Implementation | Apply fixes | 55-75 min |
| 5. Testing | Validate changes | 75-90 min |
| 6. Documentation | Update best practices | 90-105 min |
| 7. Optimization | Fine-tune performance | 105-115 min |
| 8. Monitoring | Setup alerts | 115-120 min |
Key Metrics Analyzed
- Agent coordination latency
- Conflict resolution time
- Resource utilization
- Workflow parallelization efficiency
- Event flow bottlenecks
Agent Coordination
Uses meta-orchestration pattern via master-strategist coordinating:
- Pattern discovery (orchestration-discoverer)
- Anti-pattern detection (pattern-analyzer)
- Architecture design (architect-supreme)
- Implementation (devops-automator)
- Testing (test-strategist)
References
- Full Execution Flow:
.claude/docs/commands/improve-orchestration-reference.md - Orchestration Config:
.claude/orchestration/config.json - Best Practices:
.claude/docs/orchestration-patterns.md
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.
- 7d ago First seen · 66 lines · 0 tokens per session scan A bf630dfce939
improve-orchestration is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 554 tokens. 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-31.
Other commands, from other repositories
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.