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 TentacleOpera/switchboard --skill external-team-leadgit clone --depth 1 https://github.com/TentacleOpera/switchboardWrote 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/tentacleopera/switchboard/external-team-lead)<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.
<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>- NVIDIA SkillSpector pass
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.00049 | $0.01970 |
| Opus 5.5 | $0.00020 | $0.00788 |
| Sonnet 5.5 | $0.00010 | $0.00394 |
| Haiku 4.5 | $0.00005 | $0.00197 |
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.
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
LocalApiServerand 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"
}
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 Changed · +7 lines · +49 tokens per session 0554533c4214
- 1mo ago Changed · +5 lines b3f825f1e520
- 1mo ago Changed · -7 lines 7af4abebe012
- 1mo ago First seen · 167 lines · 0 tokens per session scan A 0b9b88dd8c53
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.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.