external-team-lead

external-team-lead is a skill for Claude Code from TentacleOpera/switchboard. It costs 49 tokens per session (1,970 once invoked), scanned A, original, MIT.

A workflow for an external agent to lead terminal-based worker agents through Switchboard, a local service for coordinating them. It uses files for team instructions and reports, and Git to check completed work.

In plain words
What is it for?
Dispatching work to terminal agents, reading their reports, and checking their code changes.
Why use it?
It defines how a lead agent can coordinate workers without its own terminal window and verify their changes.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents; installed under .agents/ (shared by several agents).

Good fit Dispatching work to terminal agents, reading their reports, and checking their code changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tentacleopera/switchboard/external-team-lead
Install

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.

Any agent
npx skills add TentacleOpera/switchboard --skill external-team-lead
Clone the repo
git clone --depth 1 https://github.com/TentacleOpera/switchboard

Made for: Claude Code.

Wrote 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.

agentmods badge for external-team-lead

README.md
[![agentmods](https://agentmods.dev/badge/skills/tentacleopera/switchboard/external-team-lead/github.svg)](https://agentmods.dev/skills/tentacleopera/switchboard/external-team-lead)
Your own site
<a href="https://agentmods.dev/skills/tentacleopera/switchboard/external-team-lead"><img src="https://agentmods.dev/badge/skills/tentacleopera/switchboard/external-team-lead/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.

agentmods 80×15 button for external-team-lead

Your own site · 80×15
<a href="https://agentmods.dev/skills/tentacleopera/switchboard/external-team-lead"><img src="https://agentmods.dev/badge/skills/tentacleopera/switchboard/external-team-lead.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,970 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.01970
Opus 5.5 $0.00020 $0.00788
Sonnet 5.5 $0.00010 $0.00394
Haiku 4.5 $0.00005 $0.00197

Measured 1mo ago against content hash 0554533c4214, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

external-team-lead 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.

.agents/skills/external-team-lead/SKILL.md · 172 lines

How it starts

The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: External Team Lead Mode

This skill defines how a non-terminal external agent (Antigravity, Cursor, Zed, IDE chat, or any chat agent with localhost CLI and filesystem access) operates as the lead of a team of terminal worker agents in Switchboard.


1. Core Operating Concept

In External-Headed Team Mode:

  • You (the external agent) are the Team Lead. You have no terminal window in the fleet; you control the team entirely via HTTP calls to Switchboard's LocalApiServer and file reads/writes in the workspace.
  • Workers are terminal agents. They execute subtasks in terminal ptys, code in worktrees/branches, and report completion by writing markdown report files to .switchboard/teams/<teamId>/reports/.
  • State and instructions persist on disk. Your instructions, roster, and active feature are stored in .switchboard/teams/<teamId>/head-prompt.md.
  • Verification is empirical. You verify code changes with git, not by trusting self-reports.
  • Plan files are the source of truth. You read them, dispatch based on them, and review against them. You never rewrite, edit, or restructure plan content. Your only write to a plan file is the completion-report append (if you are also coding), never a rewrite of the plan's content sections.
  • Lead-Paced Pipeline. When your current feature passes review, you pull the next staged card with POST /kanban/queue/next.

2. API Access

All interactions with Switchboard go through the switchboard CLI (switchboard api <METHOD> <path> [jsonBody]). Verify Switchboard is running:

switchboard api GET /health

3. Team Initialization

To create an external-headed team:

switchboard api POST /teams/create-external '{
  "template": "Coding",
  "headName": "<your-agent-name>",
  "featureId": "<optional-feature-id>"
}'

Response returns:

{
  "success": true,
  "teamId": "team_<your-agent-name>",
  "workers": [ ... ],
  "headPromptFile": ".switchboard/teams/team_<your-agent-name>/head-prompt.md",
  "reportsDir": ".switchboard/teams/team_<your-agent-name>/reports"
}

Read the full file on GitHub · 172 lines

Changes

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.

  1. 1mo ago Changed · +7 lines · +49 tokens per session 0554533c4214
  2. 1mo ago Changed · +5 lines b3f825f1e520
  3. 1mo ago Changed · -7 lines 7af4abebe012
  4. 1mo ago First seen · 167 lines · 0 tokens per session scan A 0b9b88dd8c53

Subscribe to this mod's changes

external-team-lead is a skill published in the GitHub repository TentacleOpera/switchboard (215 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,970 once invoked, about $0.0002 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-30.