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 switchboard-remotegit 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/switchboard-remote)<a href="https://agentmods.dev/skills/tentacleopera/switchboard/switchboard-remote"><img src="https://agentmods.dev/badge/skills/tentacleopera/switchboard/switchboard-remote/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/switchboard-remote"><img src="https://agentmods.dev/badge/skills/tentacleopera/switchboard/switchboard-remote.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.00032 | $0.06100 |
| Opus 5.5 | $0.00013 | $0.02440 |
| Sonnet 5.5 | $0.00006 | $0.01220 |
| Haiku 4.5 | $0.00003 | $0.00610 |
Grade A, and why
switchboard-remote 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 — 441 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connections & Remote Switchboard Session Entry Point
You are entering a Connections & Remote Switchboard planning session. Drive board planning either remotely (away from desk) or side-by-side using external AI surfaces (e.g. Gemini Spark or Claude Cowork). Plans live in Linear, Notion, or external file return paths. MCP or file watchers serve as the integration layer.
This is the external/remote counterpart to /sw (switchboard-chat). Use /sw when you have local access; use /sw-remote for external surfaces or away-from-desk control.
1. Confirm Remote Context
Check which MCP servers are connected (Linear, Notion, GitHub):
- Report what's available and note any missing connections.
- If neither Linear nor Notion is connected, warn the user that remote planning won't
be possible and offer to fall back to
/swif the user has local access.
2. Remote-Mode Rules
- Plans are stored in Linear/Notion — do NOT write
.mdfiles to.switchboard/plans/or commit to a branch for planning work. - Use
list_issues(Linear) / Notion database queries to read the current kanban state (not localkanban.dborkanban-board.md). - To improve a plan: use
/improve-remote-plan(not/improve-plan). - To create a new plan: write directly to a new Linear issue or Notion page, set status to "Created".
- Column transitions happen via status updates in Linear/Notion — the extension picks them up on next IDE startup via the startup reconciler.
- To trigger local execution: set the Linear/Notion status to the execution-trigger
state (confirm the name with
list_issue_statusesfirst for Linear; read theKanban Columnselect options for Notion).
2a. The remote command vocabulary is closed at two verbs
A remote surface may author content and move a card. Nothing else. There
is no third verb, and there is no free-text instruction channel — not as a
setting, not as an advanced toggle. ALLOWED_REMOTE_VERBS in
src/services/remote/RemoteCommandEnforcement.ts is the definition, and
test:contract:remote-command-vocabulary fails CI if it grows.
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 · +55 lines 982e006fe5d4
- 1mo ago Changed · +33 lines 66ee861c7e6b
- 1mo ago First seen · 353 lines · 32 tokens per session scan A 489cba3b99cf
switchboard-remote is a skill published in the GitHub repository TentacleOpera/switchboard (215 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 6,100 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-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.