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 atman-33/workhub --skill launch-teamgit clone --depth 1 https://github.com/atman-33/workhubWrote 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/atman-33/workhub/launch-team)<a href="https://agentmods.dev/skills/atman-33/workhub/launch-team"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/launch-team/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/atman-33/workhub/launch-team"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/launch-team.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.00028 | $0.00872 |
| Opus 5.5 | $0.00011 | $0.00349 |
| Sonnet 5.5 | $0.00006 | $0.00174 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
launch-team 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch a team of Claude Code agents — one persistent session per pane — to work a single task together. You are the conductor: pick the roles, write the brief, start the team. From there the agents coordinate themselves, each messaging teammates by typing into their panes. launcher.mjs does the deterministic setup (panes, role prompts, the shared roster); your judgment is the roles and the brief.
This skill only works inside a supported multiplexer session (herdr or zellij). The transport is selected automatically (herdr is the default; override via transport.config.json). If no multiplexer session is active, stop and tell the user to start herdr (or zellij) first.
Step 1 — Decide the team
From the arguments, settle the roles and how many agents. One agent is the orchestrator (decomposes the task, delegates, integrates); the rest are workers. If the user gave only a task, propose a default and confirm:
orchestrator— Designer & Orchestratorimplementer— Implementerreviewer— Reviewer
Use lowercase kebab-case ids (they become pane names). Keep the team to 2–4 agents.
Done when: the agent ids, their roles, and which one is the orchestrator are settled.
Step 2 — Write the brief and config
Write a brief: a self-contained description of the goal. Reference existing artifacts (PRDs, plans, issues, diffs) by path/URL instead of pasting them; redact secrets.
Then write a config JSON to the OS temp directory (not the workspace):
{
"team": "feature-x",
"brief": "<the full brief>",
"agents": [
{ "id": "orchestrator", "role": "Designer & Orchestrator", "orchestrator": true, "focus": "plan and coordinate" },
{ "id": "implementer", "role": "Implementer", "focus": "write the code" },
{ "id": "reviewer", "role": "Reviewer", "focus": "review diffs and flag issues" }
]
}
Done when: the config JSON is saved and its absolute path is captured.
Step 3 — Launch the team
Run the launcher by its absolute path — do NOT cd into the skill directory. Pass --cwd set to the project directory the team works on (not the skill directory):
What ships with it
6 files 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.
- 1mo ago First seen · 65 lines · 28 tokens per session scan A fc085ef36ef3
launch-team is a skill published in the GitHub repository atman-33/workhub (3 stars, last pushed 3d ago), licensed MIT. It adds 28 tokens to every session and 872 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-09-03.
Other skills, from other repositories
gonavi-cli
Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…
readmd-skill-creator
Use when a ReadMD user wants to design, test, or improve a reusable document-writing Skill.
avoid-ai-writing
Use when outward-facing Markdown should avoid recognizable machine-written patterns while retaining its claims.
readmd-proofread
Use when a Markdown document needs publication-grade language, punctuation, and format proofreading.
research-paper-writing
Use when a research Markdown document needs a rigorous argument, evidence chain, or publication-ready section.
expo-launchpad-evaluator
Phase A, step 6 — skeptical QA. Run the app, watch it, then judge against the contract. Default = functional check; --strict adds quality scoring and an edge-case sweep.