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 query-kanbangit 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/query-kanban)<a href="https://agentmods.dev/skills/tentacleopera/switchboard/query-kanban"><img src="https://agentmods.dev/badge/skills/tentacleopera/switchboard/query-kanban/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/query-kanban"><img src="https://agentmods.dev/badge/skills/tentacleopera/switchboard/query-kanban.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 113 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Agent Snooping · line 149 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00056 | $0.02708 |
| Opus 5.5 | $0.00022 | $0.01083 |
| Sonnet 5.5 | $0.00011 | $0.00542 |
| Haiku 4.5 | $0.00006 | $0.00271 |
Grade A, and why
query-kanban 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Query Kanban
Read kanban board state. READ-ONLY — this skill never writes. Card moves go through
the kanban_operations skill (move-card.js / POST /kanban/move), never through SQL.
Preconditions
The primary method is the LocalApiServer read endpoints, reached through the Switchboard CLI. You need:
- A running Switchboard host — the VS Code extension with its API server, or the
standalone/npx host. Probe it exactly the way
manage-featuresdoes:switchboard api GET /health # -> { status: 'ok', port, roots: [...] } - Nothing else. The CLI owns port discovery, the
/healthprobe and token attachment. Do not resolve a port yourself.
When absent — switchboard api reports no running Switchboard: say so and stop.
The board is not reachable from this session. That is not a fault and not
something to route around: it is expected in a cloud VM, a tracker-only session, or on a
machine where the extension is not open. Report it as the configuration fact it is, then
ask the user to start the host. Do not hand-write SQL to compensate, and do not
report an empty board.
Why endpoints and not the file.
.gitignoreignores.switchboard/*, so a fresh per-feature worktree checkout has no database and no port file at all — a direct read from inside a worktree is broken today, not eventually. The endpoints work from any directory because the CLI finds the host, not the file. The endpoints also span the board's storage window (see below), canonicalise column ids, and honour the resolve-only project semantics; a raw file read does none of that.
Primary method — the LocalApiServer read endpoints
Every read returns { "success": true, "data": <payload> }.
| Endpoint | Returns |
|---|---|
GET /kanban/board |
Every active plan record for the workspace |
GET /kanban/plans?column=<id> |
Plans in one column (storage id, URL-encoded) |
GET /kanban/plans?featureId=<id> |
Subtasks of a feature |
GET /kanban/plan?planId=<id> |
One plan record, its file content (.data.content), and .data.source |
GET /kanban/columns |
The live {id, label, enabled, enabledSource} catalogue — built-in and custom |
GET /kanban/features |
All features (isFeature rows) |
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 · -3 lines ab35459e5e7a
- 1mo ago Changed · +7 lines · +56 tokens per session 1262832e44b7
- 1mo ago Changed · -119 lines 8caa6e25e139
- 1mo ago Changed · +24 lines 2eeb2d341e3d
- 1mo ago First seen · 302 lines · 0 tokens per session scan A 2e3fe277e56d
query-kanban is a skill published in the GitHub repository TentacleOpera/switchboard (215 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 2,708 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.