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/pattyboi101/indiestack/orchestrategit clone --depth 1 https://github.com/Pattyboi101/indiestackWrote 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/pattyboi101/indiestack/orchestrate)<a href="https://agentmods.dev/commands/pattyboi101/indiestack/orchestrate"><img src="https://agentmods.dev/badge/commands/pattyboi101/indiestack/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.00377 |
| Opus 5 | $0.00000 | $0.00188 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00038 |
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 4d 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.
What it actually says
Orchestrate — Multi-Department Agent Dispatch
Run the IndieStack orchestrator to delegate a task across department agents.
Usage
The user provides a task after /orchestrate. If no task is given, ask them what they want done.
Run
cd ~/indiestack && python3 .orchestra/orchestrator.py --simple "$ARGUMENTS"
The orchestrator will:
- Decompose the task into department assignments (Master, Opus)
- Route through Strategy & QA for approval/challenge/veto (Opus)
- Dispatch approved work to department agents in parallel (Sonnet/Haiku)
- Update memory and save run history
Departments
- Frontend — routes, components, HTML/CSS
- Backend — db.py, auth, payments, scripts
- DevOps — Dockerfile, fly.toml, smoke tests
- Content/SEO — copy, meta tags, JSON-LD
- MCP/Integration — mcp_server.py, PyPI
- Strategy & QA — reviews everything, can veto
After completion
- Report what each department did and what S&QA flagged
- Show total cost (equivalent, not actual — we're on subscription)
- Check if any files were changed:
git status --short - Ask the user if they want to commit the changes
Notes
- Config:
.orchestra/config.json(budget cap, models, department scopes) - Memory grows in
.orchestra/memory/— orchestrator gets smarter over time - Logs in
.orchestra/logs/, history in.orchestra/history/ - For the curses dashboard version, user can run directly:
python3 .orchestra/orchestrator.py "task"
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.
- 4d ago First seen · 43 lines · 0 tokens per session scan A 32f8ad7e7e3e
orchestrate is a command published in the GitHub repository Pattyboi101/indiestack (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 377 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.