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 skills add krzysztofsurdy/code-virtuoso --skill dispatching-agent-teamsgit clone --depth 1 https://github.com/krzysztofsurdy/code-virtuosoWrote 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/skills/krzysztofsurdy/code-virtuoso/dispatching-agent-teams)<a href="https://agentmods.dev/skills/krzysztofsurdy/code-virtuoso/dispatching-agent-teams"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/dispatching-agent-teams/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/skills/krzysztofsurdy/code-virtuoso/dispatching-agent-teams"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/dispatching-agent-teams.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.00077 | $0.01874 |
| Opus 5 | $0.00039 | $0.00937 |
| Sonnet 5 | $0.00015 | $0.00375 |
| Haiku 4.5 | $0.00008 | $0.00187 |
Grade A, and why
dispatching-agent-teams 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dispatching Agent Teams
Read a team definition file, resolve its agents and skills, and execute the coordination protocol. The team file is the recipe - this skill is the cook.
Core Principles
| Principle | Meaning |
|---|---|
| Team file is the contract | Follow the workflow, entry/exit criteria, and coordination rules defined in the team file. Do not improvise the process. |
| Detect capabilities first | Check what spawning mode the platform supports before dispatching. Peer mode if available, sequential fallback otherwise. |
| Skills before agents | Preload the team's bundled skills before spawning any agent. Agents need their reference material from the start. |
| Respect coordination rules | If the team file says "Architect must approve before implementation starts", enforce it. Do not skip gates. |
| Fail early, not late | If a required agent is not installed, stop before dispatching. Do not discover missing agents mid-workflow. |
Workflow
Phase 1: Resolve the Team
Teams are discovered from two locations in this order:
- Project teams -
teams/{name}.mdat the user's project root (user-authored teams) - Library teams - bundled with the
agent-teamsskill atskills/tools/agent-teams/teams/{name}.md(or wherever the agent-teams skill is installed)
Resolution:
- If the user provided a team name as argument, search project teams first, then the library. Project teams override library teams when names collide.
- If no argument, scan both locations and present a selection menu showing which are library teams vs project teams.
- Read the team file's YAML frontmatter:
name,lead,agents,skills,workflow. - Verify every agent in the
agentslist exists as an installed agent definition. - Verify every skill in the
skillslist exists as an installed skill. - If any agent or skill is missing, report what is missing and stop. Do not proceed with a partial team.
Team Library
The agent-teams skill catalogs the available pre-composed teams (development-team, review-squad, war-room) with their purpose and use cases. To browse what is available before dispatching, consult that skill first.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 163 lines · 77 tokens per session scan A de116e645d0a
dispatching-agent-teams is a skill published in the GitHub repository krzysztofsurdy/code-virtuoso (21 stars, last pushed 3mo ago), licensed MIT. It adds 77 tokens to every session and 1,874 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks OpenClaw to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
trello
Manage Trello boards, lists, and cards via the Trello REST API.
survey
A project-discovery workflow that creates `.claude/context.md`, a shared file describing the project's purpose, design, constraints, and measures of success.
dev-plan
Full development planning pipeline. Orchestrates a team of agents (researcher, prd-writer, software-architect, project-planner, issue-estimator) to take a project idea from concept to sprint-ready issues.
hermes-overnight-autonomy
Use for unattended Hermes continuity and watchdogs.
github-issues
Create, search, triage, and manage GitHub issues. Each section shows gh first, then the curl fallback.