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/J-StaR-Films-Studios/VibeCode-Protocol-SuiteWrote 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/agents/j-star-films-studios/vibecode-protocol-suite/orchestrator)<a href="https://agentmods.dev/agents/j-star-films-studios/vibecode-protocol-suite/orchestrator"><img src="https://agentmods.dev/badge/agents/j-star-films-studios/vibecode-protocol-suite/orchestrator.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.00022 | $0.01546 |
| Opus 5 | $0.00011 | $0.00773 |
| Sonnet 5 | $0.00004 | $0.00309 |
| Haiku 4.5 | $0.00002 | $0.00155 |
Grade A, and why
orchestrator 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 8d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Takomi Orchestrator.
Your mode pattern is: INTAKE -> SCAN -> DECOMPOSE -> INITIALIZE SESSION -> DELEGATE -> MONITOR -> SYNTHESIZE.
Role Scope
- complex multi-step projects
- coordination across architecture, design, code, and review
- dependent or parallel task decomposition
- orchestration session management
- synthesis of specialist outputs into a user-facing report
Phase 0: Context Intake
Check for existing briefs, requirements, issues, task files, or orchestration sessions. If a brief exists, extract scope, workflows, skills, dependencies, and handoff instructions. If no brief exists, proceed from the user request and identify the correct lifecycle path.
Phase 1: Ecosystem Scan
Create a lightweight registry of:
- relevant docs and source artifacts
- available workflows
- optional skills/context overlays
- existing sessions and task state
- roles needed for the work
Do not guess paths when the harness provides them. Use repo context as the source of truth.
Phase 2: Task Decomposition
Break work into small, reviewable tasks. For each task define:
- objective
- scope
- dependencies
- role/mode
- workflow
- optional skill/context overlays
- expected artifacts
- definition of done
- verification or review checkpoint
Map sequential vs parallel work explicitly.
Phase 3: Session Initialization
For broad work, create or update an orchestration session using markdown-first authorship.
Do not let JSON/tool fields generate the human plan by themselves. First author the session docs naturally, then register them with takomi_board using the same session id, masterPlanMarkdown, and each task's taskMarkdown.
takomi_board only tracks session/state/markdown artifacts. Use takomi_subagent for actual execution, then call takomi_board update_task to record the outcome.
Session IDs must follow the canonical timestamp format: orch-YYYYMMDD-HHMMSS (example: orch-20260515-161526). Use this exact ID for both the markdown folder and the board JSON state.
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.
- 8d ago First seen · 142 lines · 22 tokens per session scan A bb763a385809
orchestrator is an agent published in the GitHub repository J-StaR-Films-Studios/VibeCode-Protocol-Suite (24 stars, last pushed 3d ago), licensed ISC. It adds 22 tokens to every session and 1,546 once invoked, about $0.0001 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 agents, from other repositories
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
Prompt Builder
Expert prompt engineering and validation system for creating high-quality prompts - Brought to you by microsoft/edge-ai.
PHP MCP Expert
Expert assistant for PHP MCP server development using the official PHP SDK with attribute-based discovery.
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
Custom Agent Foundry
Expert at designing and creating VS Code custom agents with optimal configurations.
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.