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 agentmods add skills/tentacleopera/switchboard/dispatch-analysisnpx skills add TentacleOpera/switchboard --skill dispatch-analysisgit clone --depth 1 https://github.com/TentacleOpera/switchboardWhat 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 | $0.00000 | $0.02574 |
| Opus 5 | $0.00000 | $0.01287 |
| Sonnet 5 | $0.00000 | $0.00515 |
| Haiku 4.5 | $0.00000 | $0.00257 |
Grade A, and why
dispatch-analysis 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 2d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dispatch Analysis — Parallel-Safety Selection for Planned Plans
Read-only analysis pass that examines all plans in the PLAN REVIEWED (Planned) column, identifies the largest subset that can safely run in parallel without file-level conflicts, and moves that subset to the STAGING column. Plans that cannot be parallelized remain in Planned. This skill never modifies plan files — it only moves cards via the API.
When This Skill Runs
This skill is dispatched by the Kanban board's Analyze button on the Planned column.
The board sends a dispatch-analysis instruction to the existing planner agent, which
routes to this skill. It is NOT invoked ad hoc by the user.
Inputs
The prompt provides:
WORKSPACE_ROOT— the workspace root pathAPI_PORT— the LocalApiServer portPROJECT— the board's active project filter (optional; see step 1)PLANS TO PROCESS— a list of candidate plan IDs/files
Steps
1. Fetch the current Planned column — scoped to the board the user is looking at
Query the API for the latest board state (the plan list in the prompt may be stale by the time analysis runs — always re-query for freshness):
GET http://localhost:{API_PORT}/kanban/board?workspaceRoot={WORKSPACE_ROOT}
Filter for cards where kanbanColumn === 'PLAN REVIEWED'.
Then scope the result — the board endpoint returns every project, the board the user pressed Analyze on does not. Analysing cards from another project stages work the user cannot see in the column they clicked, which is never what they asked for.
| Prompt carries | Scope the re-queried Planned column to |
|---|---|
PROJECT=<name> |
cards where project === <name> |
PROJECT=<unassigned> |
cards with an empty project |
PROJECT=<all> |
every card — the user is viewing the unfiltered board |
no PROJECT line |
exactly the plans listed in PLANS TO PROCESS — do not widen |
The re-query is for freshness (a card may have moved, a plan may have been edited) and to catch late additions inside that scope. It is never a licence to analyse a wider set than the prompt described.
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.
- 2d ago First seen · 199 lines · 0 tokens per session scan A 83115ec24cd5
dispatch-analysis is a skill published in the GitHub repository TentacleOpera/switchboard (213 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,574 tokens. 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.