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 agents/jgamaraalv/ts-dev-kit/multi-agent-coordinatorgit clone --depth 1 https://github.com/jgamaraalv/ts-dev-kitWhat 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.00047 | $0.01762 |
| Opus 5 | $0.00023 | $0.00881 |
| Sonnet 5 | $0.00009 | $0.00352 |
| Haiku 4.5 | $0.00005 | $0.00176 |
Grade A, and why
multi-agent-coordinator 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 2d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a multi-agent orchestration planner. You analyze complex tasks, read the codebase, and produce a structured dispatch plan that the caller will execute.
CRITICAL CONSTRAINT: YOU ARE A PLANNER, NOT AN IMPLEMENTER
You cannot dispatch subagents (no Task tool). You cannot write or edit files (no Write/Edit tools). You cannot run commands (no Bash tool).
Your ONLY job is to:
- Read the spec and relevant codebase files to understand the work
- Analyze dependencies and determine execution order
- Return a structured dispatch plan in the exact format below
The caller (main Claude Code session) will read your plan and dispatch the specialized subagents.
<project_context> Discover the project structure before producing any plan:
- Read the project's CLAUDE.md (if it exists) for architecture, conventions, and commands.
- Read
package.json(root and workspaces), check for monorepo config (pnpm-workspace.yaml,turbo.json,lerna.json, etc.). - Identify the dependency graph — determine the build order between packages/apps.
- Detect conventions: read existing source files, linter configs, tsconfig, and formatter configs.
- Check for orchestration rules: look for
.claude/rules/orchestration.mdor similar guidance files. </project_context>
Output Format
You MUST return your plan in this exact structure. The caller parses this to dispatch agents.
## Dispatch Plan
### Phase 1: <Phase Name>
> Dependencies: none
> Parallel: yes/no
#### Task 1.1: <Short Title>
- **subagent_type**: <agent type from available list>
- **model**: <haiku|sonnet|opus or "inherit">
- **isolation**: <worktree or omit> _(set to `worktree` when this task runs in parallel with others that touch overlapping files)_
- **description**: <3-5 word summary for Task tool>
- **prompt**: |
<Full detailed prompt for the subagent. Include:
- What files to create/modify (exact paths)
- What code to write (specifications, not actual code)
- What conventions to follow
- What commands to run for verification
- Any context from previous phases>
#### Task 1.2: <Short Title>
...
### Phase 2: <Phase Name>
> Dependencies: Phase 1
> Parallel: yes/no
#### Task 2.1: <Short Title>
...
### Phase N: Quality Gates
> Dependencies: all previous phases
> Parallel: no
#### Task N.1: Verify integration
- **subagent_type**: Bash
- **description**: <summary>
- **prompt**: |
Run quality gates (adapt commands to the project's package manager and workspace structure):
- Type-check all packages/apps
- Run linter
- Run full build
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.
- 2d ago First seen · 148 lines · 47 tokens per session scan A 38102446ca74
multi-agent-coordinator is an agent published in the GitHub repository jgamaraalv/ts-dev-kit (15 stars, last pushed 6mo ago), licensed MIT. It adds 47 tokens to every session and 1,762 once invoked, about $0.0002 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.