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/manage-featuresnpx skills add TentacleOpera/switchboard --skill manage-featuresgit 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/manage-features)<a href="https://agentmods.dev/skills/tentacleopera/switchboard/manage-features"><img src="https://agentmods.dev/badge/skills/tentacleopera/switchboard/manage-features.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00000 | $0.06572 |
| Opus 5 | $0.00000 | $0.03286 |
| Sonnet 5 | $0.00000 | $0.01314 |
| Haiku 4.5 | $0.00000 | $0.00657 |
Grade A, and why
manage-features scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "$BASE/kanban/plans?featureId=<featurePlanId>" | jq '.data[] | {planId, topic, planFile, kanbanColumn}' How it starts
The opening of the file, as written. The whole thing — 486 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Features
Create, group, and rearrange Switchboard features. This skill consolidates four feature-management operations into one discoverable skill:
- Create — write a feature file directly (remote-session fallback when the extension is not running).
- Create from Plans — create a feature from a known set of plans via
create-feature.js(extension running). - Group — scan pre-coding columns, cluster loose plans by capability, propose groupings for one approval, then create features.
- Rearrange — restructure a feature's subtasks (split/move/merge/reorder) without rewriting their content.
When a directive says "invoke the manage-features skill and follow the
Create from Plans section", jump to that section below.
Create
Create a Switchboard feature by writing the feature file directly to
.switchboard/features/. Use this section when you are in a remote session
(Claude Code web, claude.ai) and the VS Code extension is not running —
create-feature.js routes through the extension's LocalApiServer and has no
direct-DB fallback, so it fails when the extension is unreachable.
When to Use
- You are in a remote session (no VS Code extension running).
- The user asks to create a new feature (grouping plans together, or a standalone feature).
- Do NOT use this section if the extension IS running — call
create-feature.jsinstead (it's authoritative: does DB upsert, subtask linking, file write, and board refresh atomically).
How to Detect Whether the Extension Is Running
- Check for
.switchboard/api-server-port.txtin the workspace root. - If present and the health endpoint responds
(
GET http://127.0.0.1:{port}/health), the extension is live — usecreate-feature.js. - If absent or health check fails, proceed with direct file write.
Feature File Format
Feature files live in .switchboard/features/ and follow this structure:
---
description: '{Feature Name}'
---
# {Feature Name}
## Goal
{Description of what this feature achieves and why it matters.}
## How the Subtasks Achieve This
{Narrative connecting the subtasks to the goal. Written once by the agent;
preserved by _regenerateFeatureFile on subsequent subtask changes.}
<!-- BEGIN SUBTASKS (auto-generated, do not edit) -->
## Subtasks
- [ ] (no subtasks)
<!-- END SUBTASKS -->
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.
- 4d ago First seen · 486 lines · 0 tokens per session scan A 4b8771e5d561
manage-features is a skill published in the GitHub repository TentacleOpera/switchboard (213 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,572 tokens. A static security scan graded it A with 1 finding (makes network calls). 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.
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
glab-issue
Create, view, update, and manage GitLab issues. Use when working with issue tracking, bug reports, feature requests, or task management. Operations include creating issues, listing with filters, viewing details, adding comments/notes, updating labels/assignees/milestones, closing/reopening, and board management.…
sales-ops
Set up and run Airtable-based sales operations and CRM workflows — pipeline management, account and renewal management, deal desk, RFP / tender pipelines, partner CRMs, sales forecasting, vertical CRMs (real estate, mortgage, brokerage, capital markets, public works, nonprofit), and AI-native lean stacks…