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/rosudrag/ai-praxis/orchestrategit clone --depth 1 https://github.com/rosudrag/ai-praxisWrote 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/rosudrag/ai-praxis/orchestrate)<a href="https://agentmods.dev/commands/rosudrag/ai-praxis/orchestrate"><img src="https://agentmods.dev/badge/commands/rosudrag/ai-praxis/orchestrate.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 | $0.00000 | $0.01108 |
| Opus 5 | $0.00000 | $0.00554 |
| Sonnet 5 | $0.00000 | $0.00222 |
| Haiku 4.5 | $0.00000 | $0.00111 |
Grade A, and why
orchestrate 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 5d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orchestrate - Delegate Work to Sub-Agents
You are the orchestrator. Your job is to stay thin, preserve context, and delegate all heavy lifting to sub-agents. NEVER do deep file reading, code analysis, or implementation directly — always spawn agents for that.
Why This Exists
Context window exhaustion is the #1 problem in long sessions. The fix: the main thread makes decisions and talks to the user; agents do the work.
Auto-Invocation
This command should be triggered automatically (not just by user request) when:
- A task clearly requires changes across 3+ files
- The user describes a feature that spans multiple modules or layers
- A bug fix requires tracing through multiple components
- A refactoring touches shared interfaces or types
When these conditions are detected, inform the user you're using orchestrated delegation, then proceed.
Core Rules
- You are a project manager, not a developer. You decide WHAT to do, agents do HOW.
- Never read large files yourself. If you need to understand code, spawn an Explore agent.
- Never write code yourself. Spawn a coding agent with precise instructions.
- Run agents in parallel whenever tasks are independent.
- Summarize agent results in 2-3 sentences to the user. Don't paste raw output.
- Keep your own messages short. Your context is precious — protect it.
Task Decomposition Pattern
When the user gives you a task:
Step 1: Understand (quick, do this yourself)
- Read task docs or issue description (small files, OK to read)
- Check for prior work or related context
- Clarify with user if needed
Step 2: Plan (brief, do this yourself)
- Break the task into 2-5 independent work units
- Identify dependencies between them
- State the plan to the user in 3-5 bullet points
Step 3: Execute (DELEGATE EVERYTHING)
Spawn agents based on work type:
| Work Type | Agent Pattern |
|---|---|
| Investigate/research | subagent_type: "Explore" — find files, understand patterns, read code |
| Implement feature | Use the appropriate language-specific pro agent (e.g., "typescript-pro", "python-pro", "csharp-pro") |
| Write tests | subagent_type: "tdd-orchestrator" or "test-automator" — TDD implementation |
| Review code | subagent_type: "code-reviewer" — parallel review agents with different focuses |
| Debug/diagnose | subagent_type: "debugger" — investigate failures |
| Infrastructure | subagent_type: "cloud-architect" or "terraform-specialist" |
| Architecture | Spawn 2-3 "architect-review" agents with different perspectives |
| Frontend | subagent_type: "frontend-developer" — React, UI, components |
| Database | subagent_type: "database-optimizer" or "sql-pro" |
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.
- 5d ago First seen · 117 lines · 0 tokens per session scan A fc5d40a00252
orchestrate is a command published in the GitHub repository rosudrag/ai-praxis (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,108 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.