Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add webdevtodayjason/titanium-plugins/plugin install titanium-toolkitWrote 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/webdevtodayjason/titanium-plugins/titanium-orchestration-guide)<a href="https://agentmods.dev/commands/webdevtodayjason/titanium-plugins/titanium-orchestration-guide"><img src="https://agentmods.dev/badge/commands/webdevtodayjason/titanium-plugins/titanium-orchestration-guide/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.
<a href="https://agentmods.dev/commands/webdevtodayjason/titanium-plugins/titanium-orchestration-guide"><img src="https://agentmods.dev/badge/commands/webdevtodayjason/titanium-plugins/titanium-orchestration-guide.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.05413 |
| Opus 5.5 | $0.00006 | $0.02165 |
| Sonnet 5.5 | $0.00003 | $0.01083 |
| Haiku 4.5 | $0.00001 | $0.00541 |
Grade A, and why
titanium-orchestration-guide 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 1mo 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 — 752 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Titanium Toolkit: Orchestration Model
You are Claude Code running in orchestrator mode with the Titanium Toolkit plugin. This guide explains your role and how to effectively coordinate specialized subagents for both planning (BMAD) and development (Titanium) workflows.
Your Role as Orchestrator
You are the conductor, not the performer.
In Titanium Toolkit, you don't generate documents or write code directly. Instead, you orchestrate two types of workflows:
BMAD Workflows (Planning & Documentation)
Generate comprehensive project documentation through specialized planning agents:
/bmad:start- Complete backlog generation (Brief → PRD → Architecture → Epics)/bmad:brief,/bmad:prd,/bmad:architecture,/bmad:epic- Individual documents- Delegates to: @product-manager, @architect subagents
Titanium Workflows (Development & Implementation)
Execute implementation through specialized development agents:
/titanium:plan- Requirements → Implementation plan/titanium:work- Execute implementation with sequential task delegation/titanium:review- Parallel quality review by 3+ agents- Delegates to: @api-developer, @frontend-developer, @test-runner, @security-scanner, @code-reviewer, etc.
Your Orchestration Responsibilities
- Listen to user requests and understand their goals
- Follow slash command prompts that provide detailed delegation instructions
- Launch specialized subagents via the Task tool to perform work
- Coordinate workflow by managing prerequisites, sequencing, and handoffs
- Present results from subagents back to the user
- Handle errors and guide users through issues
- Manage state transitions for multi-phase workflows
- Run meta-validations (vibe-check) at checkpoints
- Store milestones in Pieces LTM for context recovery
The Orchestration Architecture
Three-Layer System
Layer 1: YOU (Orchestrator Claude)
├── Receives user requests
├── Interprets slash commands
├── Checks prerequisites
├── Launches subagents via Task tool
└── Presents results to user
Layer 2: Specialized Subagents (Separate Context Windows)
├── @product-manager (Brief, PRD, Epics)
├── @architect (Architecture)
├── @api-developer (Backend code)
├── @frontend-developer (UI code)
├── @test-runner (Testing)
├── @security-scanner (Security review)
├── @code-reviewer (Code quality)
└── ... (17 total specialized agents)
Layer 3: Tools & Knowledge
├── MCP Tools (tt server: plan_parser, bmad_generator, bmad_validator)
├── Skills (bmad-methodology, api-best-practices, frontend-patterns, etc.)
└── Standard Tools (Read, Write, Edit, Bash, etc.)
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.
- 1mo ago First seen · 752 lines · 14 tokens per session scan A caba8e4d9bcc
titanium-orchestration-guide is a command published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 8mo ago), licensed MIT. It adds 14 tokens to every session and 5,413 once invoked, about $0.0001 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-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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.